Conversion from 3 Gibibits per second to Megabits per second

=

Invert

Formula to convert Gibibits per second (Gibit/s) to Megabits per second (Mbit/s)

More information

Gibibits per second to Megabits per second conversion table

Gibibits per second (Gibit/s)Megabits per second (Mbit/s)
1 Gibibit per second1073.741824 Mbit/s
2 Gibibits per second2147.483648 Mbit/s
3 Gibibits per second3221.225472 Mbit/s
4 Gibibits per second4294.967296 Mbit/s
5 Gibibits per second5368.70912 Mbit/s
10 Gibibits per second10737.41824 Mbit/s
20 Gibibits per second21474.83648 Mbit/s
25 Gibibits per second26843.5456 Mbit/s
50 Gibibits per second53687.0912 Mbit/s
100 Gibibits per second107374.1824 Mbit/s

Data-transfer rate reference points

ReferenceGibibits per second (Gibit/s)Megabits per second (Mbit/s)
A dial-up modem0.0000521541 Gibit/s0.056 Mbit/s
Typical home broadband0.0931323 Gibit/s100 Mbit/s
Gigabit Ethernet0.931323 Gibit/s1000 Mbit/s
Streaming a 4K film0.0232831 Gibit/s25 Mbit/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 Megabit per second (Mbit/s)

The megabit per second is a unit of data transfer rate equal to one million bits per second. Its symbol is Mbit/s, often written Mbps. It is the unit in which internet connections are sold, which makes it the data unit most people encounter by name.

Because it is a decimal million and not 1,048,576, the conversion to octets is exact and easy: one megabit per second is 125 kilooctets per second, so a hundred-megabit connection delivers about 12.5 megaoctets per second at best. Anyone who watches a file transfer and does the division has understood the entire relationship between how connections are advertised and how transfers are reported.

What a household actually needs is far below what it usually buys. Standard-definition video streaming uses about 3 megabits per second, high definition about 5, and ultra-high definition about 25. A video call is around 3 to 8. A large family watching four separate high-definition streams while somebody downloads a game is using perhaps 60 megabits per second, which a hundred-megabit connection handles comfortably.

The reason to buy more capacity than that is not peak speed but behaviour under load. A link that is near its limit develops queues, and queues add delay, which shows up as stutter in video calls and lag in games. A connection with generous headroom keeps its latency low, and that is a more noticeable improvement than a higher number on a speed test.

Wired local networks pass through this range on the way up. The original Ethernet ran at 10 megabits per second, its successor at 100, and both were the standard office connection for a decade each before gigabit replaced them. Wireless standards followed the same path with a lag, and both are now measured in hundreds of megabits or in gigabits.

Real throughput is always below the nominal rate. Protocol overhead takes 5 to 10 per cent on a wired link; a shared wireless channel loses much more, because the medium is divided between all the devices using it and interference forces retransmission. A connection advertised at 100 megabits per second measured at 90 over cable and 50 over a busy wireless network is behaving normally.

One megabit per second equals 1,000,000 bits per second, 125 kilooctets per second, or about 0.9537 mebibits per second.