| Tebioctets per second (Tio/s) | Yobibits per second (Yibit/s) |
|---|---|
| 1 Tebioctet per second | 7.27595761418 × 10-12 Yibit/s |
| 2 Tebioctets per second | 1.45519152284 × 10-11 Yibit/s |
| 3 Tebioctets per second | 2.18278728426 × 10-11 Yibit/s |
| 4 Tebioctets per second | 2.91038304567 × 10-11 Yibit/s |
| 5 Tebioctets per second | 3.63797880709 × 10-11 Yibit/s |
| 10 Tebioctets per second | 7.27595761418 × 10-11 Yibit/s |
| 20 Tebioctets per second | 1.45519152284 × 10-10 Yibit/s |
| 25 Tebioctets per second | 1.81898940355 × 10-10 Yibit/s |
| 50 Tebioctets per second | 3.63797880709 × 10-10 Yibit/s |
| 100 Tebioctets per second | 7.27595761418 × 10-10 Yibit/s |
| Reference | Tebioctets per second (Tio/s) | Yobibits per second (Yibit/s) |
|---|---|---|
| A dial-up modem | 0.00000000636646 Tio/s | 4.63221 × 10-20 Yibit/s |
| Typical home broadband | 0.0000113687 Tio/s | 8.27181 × 10-17 Yibit/s |
| Gigabit Ethernet | 0.000113687 Tio/s | 8.27181 × 10-16 Yibit/s |
| Streaming a 4K film | 0.00000284217 Tio/s | 2.06795 × 10-17 Yibit/s |
The tebioctet per second is a unit of data transfer rate equal to 1,024 gibioctets per second, or two to the fortieth power octets per second. Its symbol is Tio/s. It is the binary counterpart of the teraoctet per second, and the two differ by 10 per cent.
Nothing outside a large machine moves data this quickly. The rate describes the memory bandwidth of an accelerator with stacked memory, the internal fabric of a high-end processor package, or the aggregate throughput of a parallel filesystem spread across thousands of drives. All of these are built from binary structures, and their totals are binary quantities divided by time.
High-performance computing is where the unit is written most often. A supercomputer's storage system is specified by how many tebioctets per second it can deliver to the compute nodes, because that number determines how quickly a simulation can save its state and resume. A machine that computes quickly but writes slowly spends its time waiting.
The ten per cent difference from the decimal unit is significant in that context. A filesystem procured to deliver 10 teraoctets per second and one delivering 10 tebioctets per second differ by a whole teraoctet per second, which in a facility of that size represents a substantial fraction of the hardware budget.
In bits a tebioctet per second is 8 tebibits per second, and in decimal terms about 1.1 teraoctets per second. Expressing the same rate four different ways is routine at this level, because the storage industry, the memory industry, the network industry and the standards bodies each prefer a different one.
For everyday comparison, a tebioctet per second would fill a large consumer hard drive in about twenty seconds. No external interface carries this; the figure describes movement between components inside a single system, where the wires are short and there are very many of them running in parallel.
Graphics processors have brought the rate within reach of a single component. A stack of high-bandwidth memory bonded directly to the processor die delivers well over a tebioctet per second to the chip that uses it, and a card carrying several such stacks passes a few. That bandwidth, rather than raw arithmetic speed, is what limits the training of large models: the arithmetic units sit idle unless the memory can keep them fed. The same reasoning explains why supercomputer designers spend as much effort on the paths between memory and processor as on the processors themselves, and why the rate is quoted in binary units when the memory it describes is addressed in powers of two.
One tebioctet per second equals 1,024 gibioctets per second, 1,099,511,627,776 octets per second, or about 1.100 teraoctets per second.
The yobibit per second is a unit of data transfer rate equal to two to the eightieth power bits per second, which is 1,024 zebibits per second. Its symbol is Yibit/s. It is the largest binary transfer rate the International Electrotechnical Commission has named, and the binary counterpart of the yottabit per second.
At this final step the binary and decimal conventions differ by 20.9 per cent, and that number is the conclusion of the argument the IEC prefixes were created to settle. A naming habit that was 2.4 per cent wrong at the kibibit has grown, through eight successive multiplications by 1.024, into a discrepancy of more than a fifth. No measurement system can carry an ambiguity that large.
The unit describes nothing. Global internet traffic runs at roughly an exabit per second, so a yobibit per second is over a million times the total communication of the human species. No link, no aggregate and no forecast reaches it, and none is expected to.
The binary series stops here because the decimal series stopped at yotta when the IEC standard was written in 1998. When ronna and quetta were added to the metric system in 2022, no matching binary names were defined, so a rate of two to the ninetieth bits per second has no accepted short form. That gap will presumably be filled if it is ever needed, which at present it is not.
Defining a rung of a ladder nobody has climbed still has a purpose. A system whose names run out forces its users to improvise, and improvised extensions conflict; writing the whole series out in advance means the rule, rather than a table of exceptions, is all anyone has to learn. That is the same reasoning that gave the metric system its complete prefix set.
For any reader of technical material the lesson of the whole binary series is a single character. Kibit/s, Mibit/s, Gibit/s, Tibit/s, Pibit/s, Eibit/s, Zibit/s and Yibit/s are binary; kbit/s, Mbit/s, Gbit/s, Tbit/s, Pbit/s, Ebit/s, Zbit/s and Ybit/s are decimal; and the difference between them widens from a rounding error to a fifth as you climb.
One yobibit per second equals 1,024 zebibits per second, 151,115,727,451,828,646,838,272 octets per second, or about 1.209 yottabits per second.