Conversion from Yobibits per second to Kibioctets per second

Information about the Yobibit per second (Yibit/s)

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.

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.