Conversion from Tebibits per second to Kibioctets per second

Information about the Tebibit per second (Tibit/s)

The tebibit per second is a unit of data transfer rate equal to 1,099,511,627,776 bits per second, which is 1,024 gibibits per second. Its symbol is Tibit/s. It is the binary counterpart of the terabit per second, and the two differ by 10 per cent.

Ten per cent is the point at which the distinction becomes a matter of money rather than of pedantry. A supplier quoting a system at a hundred terabits per second and a customer measuring a hundred tebibits per second are not describing the same performance, and the difference is ten terabits — more than most organisations' entire external connectivity.

The rate belongs to the interior of very large machines. The aggregate memory bandwidth of a rack of accelerators, or the internal switching capacity of a large network chip, reaches this range, and both are built from power-of-two structures: memory channels of fixed binary width, switch ports in powers of two, buffers sized in binary. Expressing their totals with binary prefixes preserves the arithmetic that produced them.

In octets a tebibit per second is 137,438,953,472, or 128 gibioctets per second. That is more than any single storage device can supply and more than any external cable carries. It is a figure that describes something happening inside a cabinet, between chips connected by short traces on a board, where the physical distance is measured in centimetres.

Optical research also brushes this range. A laboratory demonstration carrying a petabit per second down one fibre is a thousand times higher, but individual wavelength channels and the electronics driving them work at tebibit-scale aggregates, and papers reporting them often state the binary figure because the underlying frame sizes are binary.

The habit of writing the lowercase i is worth keeping even where the reader is unlikely to check. A number written unambiguously can be converted correctly by anyone who reads it later; one written ambiguously cannot be repaired, and at ten per cent the ambiguity is no longer harmless.

One tebibit per second equals 1,024 gibibits per second, 137,438,953,472 octets per second, or about 1.100 terabits per second.

Information about the Kibioctet per second (Kio/s)

The kibioctet per second is a unit of data transfer rate equal to 1,024 octets per second, and therefore to 8,192 bits per second. Its symbol is Kio/s. Unlike most of the binary rate units it is genuinely common, because the command-line tools that copy, download and synchronise files have reported in it for decades.

The reason is straightforward. Those tools count what they have moved in blocks, and blocks are powers of two. A program that reads in four-kibioctet pieces and divides the total by elapsed time produces a rate in kibioctets per second, and reporting it in decimal kilooctets would require an extra multiplication for no benefit. The unit is what the arithmetic naturally produces.

Anyone who has watched a file copy on a Unix-like system has seen the figure. Download utilities, archive tools, disc-writing commands and network file transfer programs all report progress in kibioctets or mebioctets per second, and most of them label it correctly with the lowercase i. It is one of the few places where the IEC prefixes are used consistently in everyday software.

For scale, a kibioctet per second moves about a thousand characters of text each second: a short letter in a second, a novel in about ten minutes. It is a rate at which a modern web page will not load in any reasonable time, so seeing it in a progress display usually means something has gone wrong with the connection rather than that the transfer is nearly finished.

The difference from a kilooctet per second is 2.4 per cent, which nobody notices. The value of using the binary unit here is not accuracy but honesty: the number came from a binary computation, and writing it with a binary prefix says so. A reader who wants the decimal figure can convert; a reader given a decimal label for a binary number cannot recover anything.

Comparing the reading with an advertised connection speed requires two steps: multiply by eight to get bits, and adjust by 2.4 per cent for the base. In practice the second step is beneath the noise of any real measurement, and the first is the one that matters.

One kibioctet per second equals 1,024 octets per second, 8,192 bits per second, or 1.024 kilooctets per second.