Conversion from Kibioctets per second to Gibibits per second

=

Invert

Formula to convert Kibioctets per second (Kio/s) to Gibibits per second (Gibit/s)

More information

Kibioctets per second to Gibibits per second conversion table

Kibioctets per second (Kio/s)Gibibits per second (Gibit/s)
1 Kibioctet per second0.00000762939453125 Gibit/s
2 Kibioctets per second0.0000152587890625 Gibit/s
3 Kibioctets per second0.0000228881835938 Gibit/s
4 Kibioctets per second0.000030517578125 Gibit/s
5 Kibioctets per second0.0000381469726562 Gibit/s
10 Kibioctets per second0.0000762939453125 Gibit/s
20 Kibioctets per second0.000152587890625 Gibit/s
25 Kibioctets per second0.000190734863281 Gibit/s
50 Kibioctets per second0.000381469726562 Gibit/s
100 Kibioctets per second0.000762939453125 Gibit/s

Data-transfer rate reference points

ReferenceKibioctets per second (Kio/s)Gibibits per second (Gibit/s)
A dial-up modem6.83594 Kio/s0.0000521541 Gibit/s
Typical home broadband12207 Kio/s0.0931323 Gibit/s
Gigabit Ethernet122070 Kio/s0.931323 Gibit/s
Streaming a 4K film3051.76 Kio/s0.0232831 Gibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

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.


Information about the Gibibit per second (Gibit/s)

The gibibit per second is a unit of data transfer rate equal to 1,073,741,824 bits per second. Its symbol is Gibit/s. It is the binary counterpart of the gigabit per second, and the two now differ by 7.4 per cent, which is enough to matter in any engineering specification.

The unit belongs to the inside of a machine rather than to the network. Memory buses, processor interconnects and the links between chips on the same board all move a power-of-two number of bits per clock cycle, so their throughput is naturally expressed with a binary prefix. A bus sixty-four bits wide clocked at a given frequency delivers a rate that is a binary multiple of that frequency.

Networking, by contrast, is decimal all the way down. Gigabit Ethernet carries exactly one thousand million bits per second, not 1,073,741,824, and the symbol rate on the wire is chosen to make that so. Confusing the two overstates a link's capacity by seven per cent, which in a capacity plan is the difference between adequate and insufficient.

In octets a gibibit per second is 134,217,728, or 128 mebioctets per second. That is close to the throughput of a fast mechanical hard drive and well below a modern solid-state drive, so it sits at the point where storage and internal buses meet and where matching their rates becomes a design question.

Benchmark tools are the commonest place to see the unit written correctly. A memory bandwidth test that allocates buffers in powers of two and measures how long they take to traverse naturally reports in gibibits or gibioctets per second, and a well-written tool says so explicitly rather than rounding to the decimal unit.

The reason to insist on the distinction here rather than lower down the scale is arithmetic. At the kibibit the gap was 2.4 per cent and could be ignored; here it is nearly a thirteenth, and it grows by a further 2.4 per cent at every step above. Getting into the habit at this level costs nothing and avoids compounding errors later.

One gibibit per second equals 1,073,741,824 bits per second, 134,217,728 octets per second, or about 1.074 gigabits per second.