Conversion from 2 Pebioctets per second to Megabits per second

=

Invert

Formula to convert Pebioctets per second (Pio/s) to Megabits per second (Mbit/s)

More information

Pebioctets per second to Megabits per second conversion table

Pebioctets per second (Pio/s)Megabits per second (Mbit/s)
1 Pebioctet per second9007199254.74 Mbit/s
2 Pebioctets per second18014398509.5 Mbit/s
3 Pebioctets per second27021597764.2 Mbit/s
4 Pebioctets per second36028797019 Mbit/s
5 Pebioctets per second45035996273.7 Mbit/s
10 Pebioctets per second90071992547.4 Mbit/s
20 Pebioctets per second180143985095 Mbit/s
25 Pebioctets per second225179981369 Mbit/s
50 Pebioctets per second450359962737 Mbit/s
100 Pebioctets per second900719925474 Mbit/s

Data-transfer rate reference points

ReferencePebioctets per second (Pio/s)Megabits per second (Mbit/s)
A dial-up modem6.21725 × 10-12 Pio/s0.056 Mbit/s
Typical home broadband0.0000000111022 Pio/s100 Mbit/s
Gigabit Ethernet0.000000111022 Pio/s1000 Mbit/s
Streaming a 4K film0.00000000277556 Pio/s25 Mbit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Pebioctet per second (Pio/s)

The pebioctet per second is a unit of data transfer rate equal to 1,024 tebioctets per second, or two to the fiftieth power octets per second. Its symbol is Pio/s. It is the binary counterpart of the petaoctet per second, and the two differ by 12.6 per cent.

The rate exists only as a total. The aggregate memory bandwidth of a whole supercomputer, or the summed capacity of the network fabric joining its cabinets, reaches this range, and both are sums over tens of thousands of components, each of which moves a few hundred gibioctets per second on its own.

Whether such a total means anything depends on the calculation being run. A problem that divides so that each node works mostly on its own data can use the full aggregate. A problem where every node must constantly consult every other cannot, and the machine's effective bandwidth falls to what the slowest shared path allows. Most of the art of parallel programming lies in getting problems into the first category.

In octets a pebioctet per second is 1,125,899,906,842,624, and in decimal terms about 1.126 petaoctets per second. The 12.6 per cent difference is the accumulated effect of five multiplications by 1.024, and it is now large enough that no report can leave the convention unstated without introducing real uncertainty.

The unit also appears in descriptions of parallel filesystems at the largest facilities, where a storage system spread across tens of thousands of drives delivers a few pebioctets per second to a compute cluster. That number determines how quickly the machine can checkpoint its state, which in turn determines how much work is lost when a component fails — and in a machine of that size, something is always failing.

For a converter the requirement is simply that the arithmetic be exact and the label preserved. Multiplying by 1,024 five times is not difficult; silently substituting the decimal prefix is the error to avoid.

One pebioctet per second equals 1,024 tebioctets per second, 1,125,899,906,842,624 octets per second, or about 1.126 petaoctets per second.


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.