| Pebioctets (Pio) | Petaoctets (Po) |
|---|---|
| 1 Pebioctet | 1.12589990684 Po |
| 2 Pebioctets | 2.25179981369 Po |
| 3 Pebioctets | 3.37769972053 Po |
| 4 Pebioctets | 4.50359962737 Po |
| 5 Pebioctets | 5.62949953421 Po |
| 10 Pebioctets | 11.2589990684 Po |
| 20 Pebioctets | 22.5179981369 Po |
| 25 Pebioctets | 28.1474976711 Po |
| 50 Pebioctets | 56.2949953421 Po |
| 100 Pebioctets | 112.589990684 Po |
| Reference | Pebioctets (Pio) | Petaoctets (Po) |
|---|---|---|
| A plain text message (160 characters) | 1.42109 × 10-13 Pio | 1.6 × 10-13 Po |
| A three-minute MP3 | 0.00000000266454 Pio | 0.000000003 Po |
| A smartphone photo | 0.00000000355271 Pio | 0.000000004 Po |
| A high-definition film | 0.00000355271 Pio | 0.000004 Po |
| A dual-layer Blu-ray disc | 0.0000444089 Pio | 0.00005 Po |
The pebioctet is a unit of digital information equal to 1,125,899,906,842,624 octets, which is 1,024 tebioctets. Its symbol is Pio. It is the binary counterpart of the petaoctet, and the two now differ by 12.6 per cent.
This is the unit in which filesystem limits are written. Several widely deployed filesystems have maximum file or volume sizes that are exact powers of two, and those limits fall in this range: sixteen tebioctets for one, a pebioctet for another, eight pebioctets for a third. The numbers are not choices made by anyone; they follow from how many bits the filesystem uses to number its blocks.
Large scientific and commercial storage systems are also sized here. A research computing centre may run a filesystem of several pebioctets across thousands of drives, and the tools that manage it report in pebioctets because the underlying allocation is binary throughout. Converting those figures to decimal units for a report introduces an error of an eighth for no benefit.
A pebioctet is roughly a thousand large consumer hard drives, or the complete video output of a broadcaster over many years. It is also close to the size of the largest single scientific archives, though those are typically stated in petaoctets by press offices and in pebioctets by the engineers who run them, which produces two different numbers for the same building.
Distinguishing the two is not pedantry at this level. A twelve per cent difference on a purchase of many pebioctets is a large sum of money, and a capacity plan built on the wrong unit will be wrong by more than the margin most plans allow. This is precisely the situation the IEC prefixes were introduced to prevent.
The symbol Pio is used in filesystem documentation, in storage system manuals and in standards. Where a source writes PB without saying which it means, the difference is an eighth, and the honest thing for a reader to do is treat the figure as approximate rather than assume one convention or the other.
One pebioctet equals 1,024 tebioctets, 1,125,899,906,842,624 octets, 8 pebibits, or about 1.126 petaoctets.
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.