Conversion from 5 Yottabits per second to Gigaoctets per second

=

Invert

Formula to convert Yottabits per second (Ybit/s) to Gigaoctets per second (Go/s)

More information

Yottabits per second to Gigaoctets per second conversion table

Yottabits per second (Ybit/s)Gigaoctets per second (Go/s)
1 Yottabit per second125000000000000 Go/s
2 Yottabits per second250000000000000 Go/s
3 Yottabits per second375000000000000 Go/s
4 Yottabits per second500000000000000 Go/s
5 Yottabits per second625000000000000 Go/s
10 Yottabits per second1.25 × 1015 Go/s
20 Yottabits per second2.5 × 1015 Go/s
25 Yottabits per second3.125 × 1015 Go/s
50 Yottabits per second6.25 × 1015 Go/s
100 Yottabits per second1.25 × 1016 Go/s

Data-transfer rate reference points

ReferenceYottabits per second (Ybit/s)Gigaoctets per second (Go/s)
A dial-up modem5.6 × 10-20 Ybit/s0.000007 Go/s
Typical home broadband1 × 10-16 Ybit/s0.0125 Go/s
Gigabit Ethernet1 × 10-15 Ybit/s0.125 Go/s
Streaming a 4K film2.5 × 10-17 Ybit/s0.003125 Go/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

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.


Information about the Gigaoctet per second (Go/s)

The gigaoctet per second is a unit of data transfer rate equal to one thousand million octets per second, or eight gigabits per second. Its symbol is Go/s. It is the unit of the fastest storage devices and of the buses inside a computer, where data moves between processor, memory and drive.

Solid-state drives on the current interface reach 3 to 14 gigaoctets per second, depending on the number of lanes they use and the generation of the bus. Each lane of the peripheral interconnect provides roughly 2 gigaoctets per second at the current generation, and a drive typically uses four of them. Doubling the generation doubles the rate, which is why the figures have risen so steadily.

Main memory is faster still. A modern memory channel delivers 30 to 60 gigaoctets per second, and a machine with several channels reaches hundreds. Graphics processors, which must feed thousands of arithmetic units at once, use memory with bandwidths measured in thousands of gigaoctets per second, at which point the unit gives way to teraoctets.

That hierarchy is what determines how a program performs. A processor can execute far more operations per second than memory can supply data for, so most fast software is written to keep data in the small fast caches rather than to fetch it repeatedly from main memory. The whole discipline of performance engineering rests on the size of these differences.

For everyday comparison, one gigaoctet per second copies a two-gigaoctet film in two seconds, and fills a one-teraoctet drive in about seventeen minutes. That is faster than the network in almost every home and faster than most external connections, so at this rate the bottleneck moves back to whatever is at the other end.

The unit also describes network links in the data centre. A ten-gigabit connection is 1.25 gigaoctets per second, a hundred-gigabit connection 12.5, and both are common between servers. Comparing a storage figure in octets with a network figure in bits requires the factor of eight, and forgetting it is how equipment gets mismatched.

One gigaoctet per second equals 1,000,000,000 octets per second, 8 gigabits per second, or about 0.9313 gibioctets per second.