| Petaoctets (Po) | Kibibits (Kibit) |
|---|---|
| 1 Petaoctet | 7812500000000 Kibit |
| 2 Petaoctets | 15625000000000 Kibit |
| 3 Petaoctets | 23437500000000 Kibit |
| 4 Petaoctets | 31250000000000 Kibit |
| 5 Petaoctets | 39062500000000 Kibit |
| 10 Petaoctets | 78125000000000 Kibit |
| 20 Petaoctets | 156250000000000 Kibit |
| 25 Petaoctets | 195312500000000 Kibit |
| 50 Petaoctets | 390625000000000 Kibit |
| 100 Petaoctets | 781250000000000 Kibit |
| Reference | Petaoctets (Po) | Kibibits (Kibit) |
|---|---|---|
| A plain text message (160 characters) | 1.6 × 10-13 Po | 1.25 Kibit |
| A three-minute MP3 | 0.000000003 Po | 23437.5 Kibit |
| A smartphone photo | 0.000000004 Po | 31250 Kibit |
| A high-definition film | 0.000004 Po | 31250000 Kibit |
| A dual-layer Blu-ray disc | 0.00005 Po | 390625000 Kibit |
The petaoctet is a unit of digital information equal to a thousand teraoctets, or a million gigaoctets. Its symbol is Po. It is the unit of institutional storage: the scale at which data belongs to an organisation rather than to a person, and at which keeping it becomes a budget line rather than an afterthought.
A petaoctet is roughly the storage of a thousand large consumer hard drives, or the text of every book ever published several times over. In video terms it is about twenty thousand hours in ultra-high definition, or two and a half years of continuous viewing. The entire catalogue of a large streaming service, held once at each quality level, comes to a few petaoctets.
Science reached this scale first. The Large Hadron Collider at CERN records tens of petaoctets a year after its trigger systems have already discarded more than 99.99 per cent of what the detectors see, and the full archive runs to several hundred petaoctets. Astronomy, genomics and climate modelling all keep archives of comparable size, and the discipline of managing them became a research field of its own.
Commercially the petaoctet describes a single data centre's storage rather than a company's total. A large organisation holds tens or hundreds of petaoctets across many sites, and the largest cloud providers hold exaoctets. At this size the practical problems are not capacity but the electricity to keep the drives spinning, the cooling, and the certainty that a fraction of the hardware is failing at any moment.
That last point drives the design. In a petaoctet array, drive failures are not exceptional events but a continuous background rate, so the system is built to lose devices constantly and rebuild without interruption. Data is stored with erasure coding across many machines, and no single copy of anything is trusted.
Reading a petaoctet is itself a problem. Even at ten gigaoctets per second, a rate few systems sustain, a full pass takes more than a day. This is why analysis at this scale is designed to move the computation to the data rather than the data to the computation, an inversion that shaped the whole field of distributed processing.
One petaoctet equals 1,000 teraoctets, 1,000,000 gigaoctets, 8 petabits, or about 0.8882 pebioctets.
The kibibit is a unit of digital information equal to 1,024 bits. Its symbol is Kibit. It is the first of the binary prefixes, a set of units defined by the International Electrotechnical Commission in 1998 to end a confusion that had run through computing since the 1960s.
The problem was straightforward. Computers address memory in powers of two, so memory came in chunks of 1,024 rather than 1,000. Engineers borrowed the metric prefix kilo for that quantity because 1,024 is close to 1,000, and for small numbers the approximation was harmless. But storage and transmission counted in true thousands, so the same prefix meant two different things depending on which part of the machine was being described.
The IEC's solution was to coin new names. Kibi is a contraction of kilo binary, and the pattern continues with mebi, gibi, tebi, pebi, exbi, zebi and yobi. Each is 1,024 times the one below, and each symbol takes the form of a capital letter followed by a lowercase i: Ki, Mi, Gi, Ti and so on. The kilobit then means one thousand bits and nothing else.
A kibibit is 128 octets, and the gap from a kilobit is 2.4 per cent. That small difference is why the two were confused for so long: at this scale nobody notices. The error compounds by 2.4 per cent at every step, reaching 5 per cent at the mebibit, 7 per cent at the gibibit and 21 per cent by the yobibit, which is where the ambiguity became genuinely expensive.
Adoption has been partial and uneven. Standards bodies, the Linux kernel and most technical documentation use the IEC prefixes correctly. Consumer software largely does not, and many programs still write KB while dividing by 1,024. The result is that a reader must often infer from context which convention a number follows, which is exactly what the standard was written to prevent.
In practice the kibibit itself appears mainly in the specifications of small memory chips, in serial memory used by embedded systems, and in protocol documents where an exact power of two matters. Anywhere the number 1,024 is meant rather than 1,000, this is the correct unit.
One kibibit equals 1,024 bits, 128 octets, or 1.024 kilobits.