| Tebioctets per second (Tio/s) | Mebioctets per second (Mio/s) |
|---|---|
| 1 Tebioctet per second | 1048576 Mio/s |
| 2 Tebioctets per second | 2097152 Mio/s |
| 3 Tebioctets per second | 3145728 Mio/s |
| 4 Tebioctets per second | 4194304 Mio/s |
| 5 Tebioctets per second | 5242880 Mio/s |
| 10 Tebioctets per second | 10485760 Mio/s |
| 20 Tebioctets per second | 20971520 Mio/s |
| 25 Tebioctets per second | 26214400 Mio/s |
| 50 Tebioctets per second | 52428800 Mio/s |
| 100 Tebioctets per second | 104857600 Mio/s |
| Reference | Tebioctets per second (Tio/s) | Mebioctets per second (Mio/s) |
|---|---|---|
| A dial-up modem | 0.00000000636646 Tio/s | 0.00667572 Mio/s |
| Typical home broadband | 0.0000113687 Tio/s | 11.9209 Mio/s |
| Gigabit Ethernet | 0.000113687 Tio/s | 119.209 Mio/s |
| Streaming a 4K film | 0.00000284217 Tio/s | 2.98023 Mio/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 mebioctet per second is a unit of data transfer rate equal to 1,048,576 octets per second, which is 1,024 kibioctets per second. Its symbol is Mio/s. It is the unit that disc benchmarks, copy tools and backup programs report in, and one of the few binary units most people see regularly without noticing.
Storage measurement produces it naturally. A benchmark writes and reads blocks whose size is a power of two, times the operation, and divides. The result is a binary rate, and reporting it as such preserves the arithmetic. A tool that converted to decimal megaoctets would introduce a 4.9 per cent adjustment for no purpose other than to match a marketing convention.
That five per cent is exactly where the two conventions diverge visibly for consumers. A drive advertised at 550 megaoctets per second and measured at 524 mebioctets per second is performing precisely as claimed; the numbers differ only because one is decimal and the other binary. A great deal of complaint about storage performance is this arithmetic misread as a shortfall.
For everyday sizes, one mebioctet per second copies a photograph in three seconds and a two-gigaoctet film in about half an hour. Modern drives run hundreds or thousands of times faster, so the unit is now the resolution at which small differences are reported rather than the scale of the whole figure.
The unit also appears in memory and cache measurements, in database throughput reports and in the output of the low-level commands that write disc images. All of these count in binary blocks because the underlying structures are binary, and all of them report in mebioctets per second because that is what the count divided by the time actually gives.
The habit of writing the lowercase i is worth keeping. It costs one character and it tells a later reader which of two conventions produced the number, which is information that cannot be recovered from context once it has been left out.
One mebioctet per second equals 1,048,576 octets per second, 1,024 kibioctets per second, or about 1.049 megaoctets per second.