Conversion from 10 Petaoctets per second to Yottabits per second

=

Invert

Formula to convert Petaoctets per second (Po/s) to Yottabits per second (Ybit/s)

More information

Petaoctets per second to Yottabits per second conversion table

Petaoctets per second (Po/s)Yottabits per second (Ybit/s)
1 Petaoctet per second0.000000008 Ybit/s
2 Petaoctets per second0.000000016 Ybit/s
3 Petaoctets per second0.000000024 Ybit/s
4 Petaoctets per second0.000000032 Ybit/s
5 Petaoctets per second0.00000004 Ybit/s
10 Petaoctets per second0.00000008 Ybit/s
20 Petaoctets per second0.00000016 Ybit/s
25 Petaoctets per second0.0000002 Ybit/s
50 Petaoctets per second0.0000004 Ybit/s
100 Petaoctets per second0.0000008 Ybit/s

Data-transfer rate reference points

ReferencePetaoctets per second (Po/s)Yottabits per second (Ybit/s)
A dial-up modem7 × 10-12 Po/s5.6 × 10-20 Ybit/s
Typical home broadband0.0000000125 Po/s1 × 10-16 Ybit/s
Gigabit Ethernet0.000000125 Po/s1 × 10-15 Ybit/s
Streaming a 4K film0.000000003125 Po/s2.5 × 10-17 Ybit/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 Yottabit per second (Ybit/s)

The yottabit per second is a unit of data transfer rate equal to a thousand zettabits per second. Its symbol is Ybit/s. For thirty years it was the largest rate the metric system could name, and it describes a speed that has no application anywhere: not in engineering, not in research, and not in any forecast that anyone takes seriously.

Its distance from reality is easy to state. Global internet traffic averages roughly one exabit per second, so a yottabit per second is about a million times the combined communication of the entire human species. The largest single link ever built runs at a few hundred terabits per second, which is a ten-billionth of this figure.

The unit is nonetheless properly defined, and that completeness is the point. The metric system's rule is that every prefix combines with every unit without exception, so a reader who has never seen Ybit/s can decode it from the prefix alone. A system with gaps would need a table of which combinations are legal, and a table is exactly what a rule-based system exists to avoid.

There is a physical way to think about the number. A yottabit per second is 125 zettaoctets per second, and the total quantity of data humanity has ever stored is a few hundred zettaoctets. A link at this rate would therefore transmit the entire accumulated information of the species in a couple of seconds. No such body of data exists in one place to be sent, and nothing at the far end could receive it.

The prefix yotta was adopted in 1991 alongside zetta, at a conference that also had to consider which letters remained free. It stood at the top of the metric ladder until 2022, when ronna and quetta were added above it, partly because data quantities were beginning to approach the old ceiling. Rates have not followed quantities upward at the same pace.

For a converter, handling the unit is a matter of consistency rather than utility. A tool that converts every metric prefix correctly does not need to decide which of them anyone will use, and a figure written in yottabits per second — however unlikely — converts by the same rule as any other.

One yottabit per second equals 1,000 zettabits per second, 125 zettaoctets per second, or about 0.8272 yobibits per second.