| Petaoctets per second (Po/s) | Exaoctets per second (Eo/s) |
|---|---|
| 1 Petaoctet per second | 0.001 Eo/s |
| 2 Petaoctets per second | 0.002 Eo/s |
| 3 Petaoctets per second | 0.003 Eo/s |
| 4 Petaoctets per second | 0.004 Eo/s |
| 5 Petaoctets per second | 0.005 Eo/s |
| 10 Petaoctets per second | 0.01 Eo/s |
| 20 Petaoctets per second | 0.02 Eo/s |
| 25 Petaoctets per second | 0.025 Eo/s |
| 50 Petaoctets per second | 0.05 Eo/s |
| 100 Petaoctets per second | 0.1 Eo/s |
| Reference | Petaoctets per second (Po/s) | Exaoctets per second (Eo/s) |
|---|---|---|
| A dial-up modem | 7 × 10-12 Po/s | 7 × 10-15 Eo/s |
| Typical home broadband | 0.0000000125 Po/s | 1.25 × 10-11 Eo/s |
| Gigabit Ethernet | 0.000000125 Po/s | 1.25 × 10-10 Eo/s |
| Streaming a 4K film | 0.000000003125 Po/s | 3.125 × 10-12 Eo/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.
The exaoctet per second is a unit of data transfer rate equal to a thousand petaoctets per second, or eight exabits per second. Its symbol is Eo/s. Nothing built runs at this rate: it is about eight times the total traffic of the entire internet, counted across every network on the planet at once.
The unit is useful mainly for thought experiments about limits. If every hard drive and flash chip manufactured in a year were read simultaneously at full speed, the combined rate would be in this range. So would the total output of every camera sensor in every phone on Earth if they all recorded at once. These are sums over the whole world's hardware, not rates any system experiences.
There is one situation in which very large data volumes really do move faster than any network, and it puts the unit in perspective. Physically shipping a container of hard drives across an ocean transfers more data per second, averaged over the journey, than any cable. A shipping container holding a few exaoctets crossing the Atlantic in a week works out to several gigaoctets per second, and a truck of drives driven across a city beats almost any local link.
That calculation is not a joke; cloud providers offer it as a service. When a customer needs to move petaoctets into a data centre, the provider ships a lorry full of storage rather than attempting the transfer over a network, because the network would take months. The bandwidth of a vehicle is enormous, though its latency is measured in days.
For the unit itself, an exaoctet per second is 125 petaoctets per second, and it would transfer the world's entire stock of stored data — a few hundred zettaoctets — in about a week of continuous running. No mechanism exists to feed such a link, and none is being designed.
A converter must nevertheless handle the unit, because it appears in aggregate capacity models, in academic papers on the theoretical limits of communication, and in any table that lists the metric prefixes completely. A quantity does not need a use for its name to be well formed.
One exaoctet per second equals 1,000 petaoctets per second, 8 exabits per second, or about 0.8674 exbioctets per second.