Conversion from Exbioctets per second to Exaoctets per second

=

Invert

Formula to convert Exbioctets per second (Eio/s) to Exaoctets per second (Eo/s)

More information

Exbioctets per second to Exaoctets per second conversion table

Exbioctets per second (Eio/s)Exaoctets per second (Eo/s)
1 Exbioctet per second1.15292150461 Eo/s
2 Exbioctets per second2.30584300921 Eo/s
3 Exbioctets per second3.45876451382 Eo/s
4 Exbioctets per second4.61168601843 Eo/s
5 Exbioctets per second5.76460752303 Eo/s
10 Exbioctets per second11.5292150461 Eo/s
20 Exbioctets per second23.0584300921 Eo/s
25 Exbioctets per second28.8230376152 Eo/s
50 Exbioctets per second57.6460752303 Eo/s
100 Exbioctets per second115.292150461 Eo/s

Data-transfer rate reference points

ReferenceExbioctets per second (Eio/s)Exaoctets per second (Eo/s)
A dial-up modem6.07153 × 10-15 Eio/s7 × 10-15 Eo/s
Typical home broadband1.0842 × 10-11 Eio/s1.25 × 10-11 Eo/s
Gigabit Ethernet1.0842 × 10-10 Eio/s1.25 × 10-10 Eo/s
Streaming a 4K film2.71051 × 10-12 Eio/s3.125 × 10-12 Eo/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Exbioctet per second (Eio/s)

The exbioctet per second is a unit of data transfer rate equal to 1,024 pebioctets per second, or two to the sixtieth power octets per second. Its symbol is Eio/s. It is the binary counterpart of the exaoctet per second, and the two differ by 15.3 per cent.

No machine, network or aggregate reaches this rate. An exbioctet per second is more than eight times the total instantaneous traffic of the entire internet, and it would move the world's whole stock of stored data in a matter of minutes. The unit describes a capacity with no source that could supply it and no destination that could take it in.

Two to the sixtieth is nevertheless a familiar number in computing, because it is the size of the address space a 64-bit machine can reach in octets divided by sixteen. The same power of two turns up in filesystem limits, in memory maps and in the design of every system built on that architecture, so the quantity is well known even though no rate approaches it.

The unit exists because the IEC series was defined completely. Every binary prefix pairs with every unit, exactly as every metric prefix does, so that a reader who has never seen Eio/s can decode it from the prefix alone. A system with gaps would need a table of permitted combinations, which is precisely what a rule-based system exists to avoid.

The difference from the decimal unit is worth restating at each level because it compounds. At the kibioctet it was 2.4 per cent, here it is more than an eighth, and at the yobioctet it will be more than a fifth. That growth is the reason the binary prefixes were created, and it is why the lowercase i has to be written even in figures nobody will check.

For a converter, the treatment is mechanical: six multiplications by 1,024 from octets, or the equivalent divisions coming down. The value of doing it correctly is not that anyone will use the result, but that a tool which handles every case the same way can be trusted on the cases that matter.

One exbioctet per second equals 1,024 pebioctets per second, 1,152,921,504,606,846,976 octets per second, or about 1.153 exaoctets per second.


Information about the Exaoctet per second (Eo/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.