Conversion from 100 Gibibits per second to Octets per second

=

Invert

Formula to convert Gibibits per second (Gibit/s) to Octets per second (octet/s)

More information

Gibibits per second to Octets per second conversion table

Gibibits per second (Gibit/s)Octets per second (octet/s)
1 Gibibit per second134217728 octet/s
2 Gibibits per second268435456 octet/s
3 Gibibits per second402653184 octet/s
4 Gibibits per second536870912 octet/s
5 Gibibits per second671088640 octet/s
10 Gibibits per second1342177280 octet/s
20 Gibibits per second2684354560 octet/s
25 Gibibits per second3355443200 octet/s
50 Gibibits per second6710886400 octet/s
100 Gibibits per second13421772800 octet/s

Data-transfer rate reference points

ReferenceGibibits per second (Gibit/s)Octets per second (octet/s)
A dial-up modem0.0000521541 Gibit/s7000 octet/s
Typical home broadband0.0931323 Gibit/s12500000 octet/s
Gigabit Ethernet0.931323 Gibit/s125000000 octet/s
Streaming a 4K film0.0232831 Gibit/s3125000 octet/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Gibibit per second (Gibit/s)

The gibibit per second is a unit of data transfer rate equal to 1,073,741,824 bits per second. Its symbol is Gibit/s. It is the binary counterpart of the gigabit per second, and the two now differ by 7.4 per cent, which is enough to matter in any engineering specification.

The unit belongs to the inside of a machine rather than to the network. Memory buses, processor interconnects and the links between chips on the same board all move a power-of-two number of bits per clock cycle, so their throughput is naturally expressed with a binary prefix. A bus sixty-four bits wide clocked at a given frequency delivers a rate that is a binary multiple of that frequency.

Networking, by contrast, is decimal all the way down. Gigabit Ethernet carries exactly one thousand million bits per second, not 1,073,741,824, and the symbol rate on the wire is chosen to make that so. Confusing the two overstates a link's capacity by seven per cent, which in a capacity plan is the difference between adequate and insufficient.

In octets a gibibit per second is 134,217,728, or 128 mebioctets per second. That is close to the throughput of a fast mechanical hard drive and well below a modern solid-state drive, so it sits at the point where storage and internal buses meet and where matching their rates becomes a design question.

Benchmark tools are the commonest place to see the unit written correctly. A memory bandwidth test that allocates buffers in powers of two and measures how long they take to traverse naturally reports in gibibits or gibioctets per second, and a well-written tool says so explicitly rather than rounding to the decimal unit.

The reason to insist on the distinction here rather than lower down the scale is arithmetic. At the kibibit the gap was 2.4 per cent and could be ignored; here it is nearly a thirteenth, and it grows by a further 2.4 per cent at every step above. Getting into the habit at this level costs nothing and avoids compounding errors later.

One gibibit per second equals 1,073,741,824 bits per second, 134,217,728 octets per second, or about 1.074 gigabits per second.


Information about the Octet per second (octet/s)

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.