| Exaoctets per second (Eo/s) | Octets per second (octet/s) |
|---|---|
| 1 Exaoctet per second | 1 × 1018 octet/s |
| 2 Exaoctets per second | 2 × 1018 octet/s |
| 3 Exaoctets per second | 3 × 1018 octet/s |
| 4 Exaoctets per second | 4 × 1018 octet/s |
| 5 Exaoctets per second | 5 × 1018 octet/s |
| 10 Exaoctets per second | 1 × 1019 octet/s |
| 20 Exaoctets per second | 2 × 1019 octet/s |
| 25 Exaoctets per second | 2.5 × 1019 octet/s |
| 50 Exaoctets per second | 5 × 1019 octet/s |
| 100 Exaoctets per second | 1 × 1020 octet/s |
| Reference | Exaoctets per second (Eo/s) | Octets per second (octet/s) |
|---|---|---|
| A dial-up modem | 7 × 10-15 Eo/s | 7000 octet/s |
| Typical home broadband | 1.25 × 10-11 Eo/s | 12500000 octet/s |
| Gigabit Ethernet | 1.25 × 10-10 Eo/s | 125000000 octet/s |
| Streaming a 4K film | 3.125 × 10-12 Eo/s | 3125000 octet/s |
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.
The octet per second is a unit of data transfer rate equal to eight bits per second. Its symbol is octet/s. It is the unit in which software reports transfer speeds, as against the bits per second in which hardware and network services advertise them, and the factor of eight between the two conventions is the source of endless confusion.
The division of labour is consistent once it is understood. Anything describing a physical link — an Ethernet port, a fibre connection, a radio channel, a broadband package — is quoted in bits per second, because bits are what the signalling actually carries. Anything describing a file moving from one place to another is quoted in octets per second, because files are measured in octets.
A download manager that reports 12 megaoctets per second on a connection sold as 100 megabits per second is not disagreeing with the advertisement; it is stating the same rate in the other convention, and the arithmetic between them is a division by eight. Recognising this immediately removes the most common cause of complaint about internet speed.
Individual octets per second appear in the same narrow places as individual bits: deep-space telemetry, low-power sensor links, and the slowest legacy serial connections. A rate of a hundred octets per second would move a page of text in about twenty seconds, which was a normal experience in the 1970s and is unimaginable now.
The unit also underlies the way disc and interface throughput is described. A drive that sustains 500 megaoctets per second is moving four gigabits per second across its interface, and matching the two figures is a routine part of system design: an interface rated in gigabits must be compared with a drive rated in octets, and the factor of eight decides whether one starves the other.
Storage tools reinforce the convention. Every file copy utility, backup program and command-line transfer tool reports in octets per second or its multiples, and every network measurement tool reports in bits per second. A person reading both at once has to keep the conversion in mind, which is exactly what makes the distinction worth stating explicitly.
One octet per second equals 8 bits per second, 0.008 kilobits per second, or 0.001 kilooctets per second.