Conversion from 10 Gibioctets per second to Pebibits per second

=

Invert

Formula to convert Gibioctets per second (Gio/s) to Pebibits per second (Pibit/s)

More information

Gibioctets per second to Pebibits per second conversion table

Gibioctets per second (Gio/s)Pebibits per second (Pibit/s)
1 Gibioctet per second0.00000762939453125 Pibit/s
2 Gibioctets per second0.0000152587890625 Pibit/s
3 Gibioctets per second0.0000228881835938 Pibit/s
4 Gibioctets per second0.000030517578125 Pibit/s
5 Gibioctets per second0.0000381469726562 Pibit/s
10 Gibioctets per second0.0000762939453125 Pibit/s
20 Gibioctets per second0.000152587890625 Pibit/s
25 Gibioctets per second0.000190734863281 Pibit/s
50 Gibioctets per second0.000381469726562 Pibit/s
100 Gibioctets per second0.000762939453125 Pibit/s

Data-transfer rate reference points

ReferenceGibioctets per second (Gio/s)Pebibits per second (Pibit/s)
A dial-up modem0.00000651926 Gio/s4.9738 × 10-11 Pibit/s
Typical home broadband0.0116415 Gio/s0.0000000888178 Pibit/s
Gigabit Ethernet0.116415 Gio/s0.000000888178 Pibit/s
Streaming a 4K film0.00291038 Gio/s0.0000000222045 Pibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Gibioctet per second (Gio/s)

The gibioctet per second is a unit of data transfer rate equal to 1,073,741,824 octets per second, which is 1,024 mebioctets per second. Its symbol is Gio/s. It is the unit of memory bandwidth and of the fastest storage interfaces, and the binary counterpart of the gigaoctet per second, from which it differs by 7.4 per cent.

Memory is where the unit belongs most naturally. A memory channel transfers a fixed number of octets per clock cycle, and that number is a power of two, so the resulting bandwidth is a binary multiple of the clock frequency. A machine with several channels reaches tens of gibioctets per second, and an accelerator with stacked memory reaches thousands.

Storage has caught up. A fast solid-state drive on the current interface sustains several gibioctets per second, which means that for the first time the drive and the memory are within an order of magnitude of each other. That convergence has changed how software is written: the old assumption that reading from disc is thousands of times slower than reading from memory no longer holds.

The unit appears in benchmark output, in system monitoring displays and in the specifications of processor interconnects. All of these count in binary because the structures they measure are binary, and reporting the result with a decimal prefix would introduce a seven per cent error for the sake of a familiar-looking label.

For a sense of what the rate means, one gibioctet per second copies a two-gigaoctet film in under two seconds and fills a one-teraoctet drive in about a quarter of an hour. Anything at this speed is faster than every external connection in an ordinary building, so the limiting factor moves inside the machine.

The distinction from the decimal unit matters most in procurement and capacity planning. A specification that requires 10 gigaoctets per second and a system that delivers 10 gibioctets per second are not the same, and the difference of 7.4 per cent is the sort of margin that decides whether a design meets its requirement.

One gibioctet per second equals 1,073,741,824 octets per second, 1,024 mebioctets per second, or about 1.074 gigaoctets per second.


Information about the Pebibit per second (Pibit/s)

The pebibit per second is a unit of data transfer rate equal to 1,024 tebibits per second, which is two to the fiftieth power bits per second. Its symbol is Pibit/s. It is the binary counterpart of the petabit per second, and the two differ by 12.6 per cent.

No deployed system runs at this rate, and the unit therefore describes either an aggregate or a laboratory result. Optical transmission records set on single fibres reach a petabit per second, and the binary figure for the same experiment is 12.6 per cent lower — a difference that matters when comparing results between papers that use different conventions.

Where the unit is genuinely appropriate is in describing structures built from powers of two. The total switching capacity of a very large network fabric, built from ports and buffers that are all binary, is a binary quantity divided by time, and reporting it in decimal units discards the arithmetic that produced it. The same applies to the summed memory bandwidth of a machine whose channel count is a power of two.

In octets a pebibit per second is 140,737,488,355,328, which is 128 tebioctets per second. That is the storage of a thousand large consumer drives moved every second, and it exists only as a total across many thousands of parallel paths inside a single facility.

The size of the discrepancy at this level is the argument for the whole IEC series in miniature. What began as a harmless 2.4 per cent at the kibibit is now an eighth, and it compounds by 2.4 per cent at every further step. A convention that was acceptable for small numbers becomes untenable for large ones, and the point of the binary prefixes is to make the distinction visible before that happens.

For a converter, the arithmetic is unremarkable: multiply or divide by 1,024 the appropriate number of times, and by eight to reach octets. What matters is that the tool does not silently substitute the decimal unit when it sees a value it cannot label precisely.

One pebibit per second equals 1,024 tebibits per second, 140,737,488,355,328 octets per second, or about 1.126 petabits per second.