Conversion from 100 Megabits per second to Pebibits per second

=

Invert

Formula to convert Megabits per second (Mbit/s) to Pebibits per second (Pibit/s)

More information

Megabits per second to Pebibits per second conversion table

Megabits per second (Mbit/s)Pebibits per second (Pibit/s)
1 Megabit per second8.881784197 × 10-10 Pibit/s
2 Megabits per second0.0000000017763568394 Pibit/s
3 Megabits per second0.0000000026645352591 Pibit/s
4 Megabits per second0.0000000035527136788 Pibit/s
5 Megabits per second0.0000000044408920985 Pibit/s
10 Megabits per second0.000000008881784197 Pibit/s
20 Megabits per second0.000000017763568394 Pibit/s
25 Megabits per second0.0000000222044604925 Pibit/s
50 Megabits per second0.000000044408920985 Pibit/s
100 Megabits per second0.00000008881784197 Pibit/s

Data-transfer rate reference points

ReferenceMegabits per second (Mbit/s)Pebibits per second (Pibit/s)
A dial-up modem0.056 Mbit/s4.9738 × 10-11 Pibit/s
Typical home broadband100 Mbit/s0.0000000888178 Pibit/s
Gigabit Ethernet1000 Mbit/s0.000000888178 Pibit/s
Streaming a 4K film25 Mbit/s0.0000000222045 Pibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Megabit per second (Mbit/s)

The megabit per second is a unit of data transfer rate equal to one million bits per second. Its symbol is Mbit/s, often written Mbps. It is the unit in which internet connections are sold, which makes it the data unit most people encounter by name.

Because it is a decimal million and not 1,048,576, the conversion to octets is exact and easy: one megabit per second is 125 kilooctets per second, so a hundred-megabit connection delivers about 12.5 megaoctets per second at best. Anyone who watches a file transfer and does the division has understood the entire relationship between how connections are advertised and how transfers are reported.

What a household actually needs is far below what it usually buys. Standard-definition video streaming uses about 3 megabits per second, high definition about 5, and ultra-high definition about 25. A video call is around 3 to 8. A large family watching four separate high-definition streams while somebody downloads a game is using perhaps 60 megabits per second, which a hundred-megabit connection handles comfortably.

The reason to buy more capacity than that is not peak speed but behaviour under load. A link that is near its limit develops queues, and queues add delay, which shows up as stutter in video calls and lag in games. A connection with generous headroom keeps its latency low, and that is a more noticeable improvement than a higher number on a speed test.

Wired local networks pass through this range on the way up. The original Ethernet ran at 10 megabits per second, its successor at 100, and both were the standard office connection for a decade each before gigabit replaced them. Wireless standards followed the same path with a lag, and both are now measured in hundreds of megabits or in gigabits.

Real throughput is always below the nominal rate. Protocol overhead takes 5 to 10 per cent on a wired link; a shared wireless channel loses much more, because the medium is divided between all the devices using it and interference forces retransmission. A connection advertised at 100 megabits per second measured at 90 over cable and 50 over a busy wireless network is behaving normally.

One megabit per second equals 1,000,000 bits per second, 125 kilooctets per second, or about 0.9537 mebibits 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.