Conversion from Petaoctets per second to Megabits per second

=

Invert

Formula to convert Petaoctets per second (Po/s) to Megabits per second (Mbit/s)

More information

Petaoctets per second to Megabits per second conversion table

Petaoctets per second (Po/s)Megabits per second (Mbit/s)
1 Petaoctet per second8000000000 Mbit/s
2 Petaoctets per second16000000000 Mbit/s
3 Petaoctets per second24000000000 Mbit/s
4 Petaoctets per second32000000000 Mbit/s
5 Petaoctets per second40000000000 Mbit/s
10 Petaoctets per second80000000000 Mbit/s
20 Petaoctets per second160000000000 Mbit/s
25 Petaoctets per second200000000000 Mbit/s
50 Petaoctets per second400000000000 Mbit/s
100 Petaoctets per second800000000000 Mbit/s

Data-transfer rate reference points

ReferencePetaoctets per second (Po/s)Megabits per second (Mbit/s)
A dial-up modem7 × 10-12 Po/s0.056 Mbit/s
Typical home broadband0.0000000125 Po/s100 Mbit/s
Gigabit Ethernet0.000000125 Po/s1000 Mbit/s
Streaming a 4K film0.000000003125 Po/s25 Mbit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Petaoctet per second (Po/s)

The petaoctet per second is a unit of data transfer rate equal to a thousand teraoctets per second, or eight petabits per second. Its symbol is Po/s. It describes the total internal bandwidth of the largest computing machines rather than any single connection, and it exists as an aggregate rather than as a rate anything can sustain on its own.

The clearest case is the interconnect of an exascale supercomputer. Such a machine has tens of thousands of nodes, each linked to the network at hundreds of gigaoctets per second, and the sum across the whole fabric reaches petaoctets per second. That figure is the reason such machines can run a single calculation spread over the whole system rather than many small independent ones.

Memory bandwidth adds up the same way. A machine with ten thousand accelerators, each with several teraoctets per second of local memory bandwidth, has tens of petaoctets per second in total. Whether that total means anything depends entirely on the calculation: a problem that can be divided so each node works mostly on its own data can use it, and a problem that cannot, cannot.

Data centre networks reach this range too. The aggregate capacity of the switching fabric inside a very large facility, counting every link between every rack, is measured in petaoctets per second. The design goal is that any server can reach any other at close to full speed, which requires far more internal capacity than the facility's external connections.

For scale, a petaoctet per second would transfer the entire contents of a large national archive in a second, or fill every hard drive manufactured in a day within about a minute. No storage system can supply data at this rate, and none can absorb it; the number describes movement inside a machine, between memory and processors, where nothing is being stored at all.

The unit also serves in optical research, where a single fibre carrying a petabit per second is 125 teraoctets per second, and an experimental system aggregating several such fibres approaches the petaoctet. Those figures come from laboratories rather than from anything deployed.

One petaoctet per second equals 1,000 teraoctets per second, 8 petabits per second, or about 0.8882 pebioctets 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.