| Tebioctets (Tio) | Petaoctets (Po) |
|---|---|
| 1 Tebioctet | 0.00109951162778 Po |
| 2 Tebioctets | 0.00219902325555 Po |
| 3 Tebioctets | 0.00329853488333 Po |
| 4 Tebioctets | 0.0043980465111 Po |
| 5 Tebioctets | 0.00549755813888 Po |
| 10 Tebioctets | 0.0109951162778 Po |
| 20 Tebioctets | 0.0219902325555 Po |
| 25 Tebioctets | 0.0274877906944 Po |
| 50 Tebioctets | 0.0549755813888 Po |
| 100 Tebioctets | 0.109951162778 Po |
| Reference | Tebioctets (Tio) | Petaoctets (Po) |
|---|---|---|
| A plain text message (160 characters) | 1.45519 × 10-10 Tio | 1.6 × 10-13 Po |
| A three-minute MP3 | 0.00000272848 Tio | 0.000000003 Po |
| A smartphone photo | 0.00000363798 Tio | 0.000000004 Po |
| A high-definition film | 0.00363798 Tio | 0.000004 Po |
| A dual-layer Blu-ray disc | 0.0454747 Tio | 0.00005 Po |
The tebioctet is a unit of digital information equal to 1,099,511,627,776 octets, which is 1,024 gibioctets. Its symbol is Tio. It is the binary counterpart of the teraoctet, and at this level the two differ by 10 per cent — the gap that produces the most familiar complaint in consumer computing.
That complaint runs as follows. A drive is sold as one teraoctet, holds exactly one million million octets, and the operating system reports 931 gigaoctets. What it is actually reporting is 0.909 tebioctets, expressed with the wrong label. Nothing is missing from the drive; the number has simply been divided by 1,024 three times and then written with a decimal prefix.
Storage administration lives in this unit. Volume sizes, RAID array capacities, snapshot reserves and quota limits are all quoted in tebioctets by the tools that manage them, because the underlying allocation units are powers of two. A filesystem asked to create a 10-teraoctet volume and one asked to create a 10-tebioctet volume will produce visibly different results.
The difference matters commercially as well as technically. Cloud storage priced per teraoctet and cloud storage priced per tebioctet differ by a tenth in the quantity delivered for the same price, and a contract that does not say which is being used is genuinely ambiguous. Careful procurement documents specify the unit explicitly for exactly this reason.
A tebioctet holds around a quarter of a million photographs, two hundred hours of high-definition video, or the complete text of every book in a large public library many times over. In a household it is more storage than a lifetime of ordinary files will use; in a video production company it is a few days of work.
The correct symbol Tio appears in filesystem tools, in storage array documentation and in standards, and it is worth using even when the audience is unlikely to notice. A figure written with a binary prefix can be converted correctly by anyone who reads it later; one written ambiguously cannot be repaired.
One tebioctet equals 1,099,511,627,776 octets, 1,024 gibioctets, 8 tebibits, or about 1.100 teraoctets.
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.