Conversion from Teraoctets per second to Kibioctets per second

=

Invert

Formula to convert Teraoctets per second (To/s) to Kibioctets per second (Kio/s)

More information

Teraoctets per second to Kibioctets per second conversion table

Teraoctets per second (To/s)Kibioctets per second (Kio/s)
1 Teraoctet per second976562500 Kio/s
2 Teraoctets per second1953125000 Kio/s
3 Teraoctets per second2929687500 Kio/s
4 Teraoctets per second3906250000 Kio/s
5 Teraoctets per second4882812500 Kio/s
10 Teraoctets per second9765625000 Kio/s
20 Teraoctets per second19531250000 Kio/s
25 Teraoctets per second24414062500 Kio/s
50 Teraoctets per second48828125000 Kio/s
100 Teraoctets per second97656250000 Kio/s

Data-transfer rate reference points

ReferenceTeraoctets per second (To/s)Kibioctets per second (Kio/s)
A dial-up modem0.000000007 To/s6.83594 Kio/s
Typical home broadband0.0000125 To/s12207 Kio/s
Gigabit Ethernet0.000125 To/s122070 Kio/s
Streaming a 4K film0.000003125 To/s3051.76 Kio/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Teraoctet per second (To/s)

The teraoctet per second is a unit of data transfer rate equal to a thousand gigaoctets per second, or eight terabits per second. Its symbol is To/s. It describes memory bandwidth inside the fastest processors and the aggregate throughput of large computing systems, rather than any link between separate machines.

Graphics and accelerator chips are the clearest example. A modern accelerator uses stacked memory placed alongside the processor on the same package, and the bandwidth between them reaches several teraoctets per second. That figure is what allows thousands of arithmetic units to be kept busy at once, and it is now the property that most often determines how fast a machine learning workload runs.

The reason bandwidth rather than arithmetic has become the limiting factor is worth stating. Processors have grown far faster at computing than memory has at supplying data, so a modern chip can perform tens of operations for every octet it reads. Any calculation that touches memory more often than that is limited by the memory, and most real calculations are.

Supercomputer interconnects reach this range in aggregate. The network joining thousands of nodes carries teraoctets per second across the whole machine, though no single link does. The design problem is to arrange the topology so that any node can reach any other quickly, which is why these networks are built as multi-dimensional meshes and trees rather than as simple stars.

To make the number concrete, one teraoctet per second would fill a large consumer hard drive in twenty seconds and transfer the entire text of every book in a national library within a minute. Nothing in ordinary use approaches it, and no external cable of any kind carries it.

The unit also appears in descriptions of storage arrays. A large parallel filesystem, spread across thousands of drives, can deliver a few teraoctets per second in aggregate to a supercomputer, and that figure is quoted as a headline specification because it determines how quickly a simulation can be written out and read back.

One teraoctet per second equals 1,000 gigaoctets per second, 8 terabits per second, or about 0.9095 tebioctets 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.