Conversion from 4 Octets per second to Pebibits per second

=

Invert

Formula to convert Octets per second (octet/s) to Pebibits per second (Pibit/s)

More information

Octets per second to Pebibits per second conversion table

Octets per second (octet/s)Pebibits per second (Pibit/s)
1 Octet per second7.1054273576 × 10-15 Pibit/s
2 Octets per second1.42108547152 × 10-14 Pibit/s
3 Octets per second2.13162820728 × 10-14 Pibit/s
4 Octets per second2.84217094304 × 10-14 Pibit/s
5 Octets per second3.5527136788 × 10-14 Pibit/s
10 Octets per second7.1054273576 × 10-14 Pibit/s
20 Octets per second1.42108547152 × 10-13 Pibit/s
25 Octets per second1.7763568394 × 10-13 Pibit/s
50 Octets per second3.5527136788 × 10-13 Pibit/s
100 Octets per second7.1054273576 × 10-13 Pibit/s

Data-transfer rate reference points

ReferenceOctets per second (octet/s)Pebibits per second (Pibit/s)
A dial-up modem7000 octet/s4.9738 × 10-11 Pibit/s
Typical home broadband12500000 octet/s0.0000000888178 Pibit/s
Gigabit Ethernet125000000 octet/s0.000000888178 Pibit/s
Streaming a 4K film3125000 octet/s0.0000000222045 Pibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Octet per second (octet/s)

The octet per second is a unit of data transfer rate equal to eight bits per second. Its symbol is octet/s. It is the unit in which software reports transfer speeds, as against the bits per second in which hardware and network services advertise them, and the factor of eight between the two conventions is the source of endless confusion.

The division of labour is consistent once it is understood. Anything describing a physical link — an Ethernet port, a fibre connection, a radio channel, a broadband package — is quoted in bits per second, because bits are what the signalling actually carries. Anything describing a file moving from one place to another is quoted in octets per second, because files are measured in octets.

A download manager that reports 12 megaoctets per second on a connection sold as 100 megabits per second is not disagreeing with the advertisement; it is stating the same rate in the other convention, and the arithmetic between them is a division by eight. Recognising this immediately removes the most common cause of complaint about internet speed.

Individual octets per second appear in the same narrow places as individual bits: deep-space telemetry, low-power sensor links, and the slowest legacy serial connections. A rate of a hundred octets per second would move a page of text in about twenty seconds, which was a normal experience in the 1970s and is unimaginable now.

The unit also underlies the way disc and interface throughput is described. A drive that sustains 500 megaoctets per second is moving four gigabits per second across its interface, and matching the two figures is a routine part of system design: an interface rated in gigabits must be compared with a drive rated in octets, and the factor of eight decides whether one starves the other.

Storage tools reinforce the convention. Every file copy utility, backup program and command-line transfer tool reports in octets per second or its multiples, and every network measurement tool reports in bits per second. A person reading both at once has to keep the conversion in mind, which is exactly what makes the distinction worth stating explicitly.

One octet per second equals 8 bits per second, 0.008 kilobits per second, or 0.001 kilooctets 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.