| Gibibits per second (Gibit/s) | Mebioctets per second (Mio/s) |
|---|---|
| 1 Gibibit per second | 128 Mio/s |
| 2 Gibibits per second | 256 Mio/s |
| 3 Gibibits per second | 384 Mio/s |
| 4 Gibibits per second | 512 Mio/s |
| 5 Gibibits per second | 640 Mio/s |
| 10 Gibibits per second | 1280 Mio/s |
| 20 Gibibits per second | 2560 Mio/s |
| 25 Gibibits per second | 3200 Mio/s |
| 50 Gibibits per second | 6400 Mio/s |
| 100 Gibibits per second | 12800 Mio/s |
| Reference | Gibibits per second (Gibit/s) | Mebioctets per second (Mio/s) |
|---|---|---|
| A dial-up modem | 0.0000521541 Gibit/s | 0.00667572 Mio/s |
| Typical home broadband | 0.0931323 Gibit/s | 11.9209 Mio/s |
| Gigabit Ethernet | 0.931323 Gibit/s | 119.209 Mio/s |
| Streaming a 4K film | 0.0232831 Gibit/s | 2.98023 Mio/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.
The mebioctet per second is a unit of data transfer rate equal to 1,048,576 octets per second, which is 1,024 kibioctets per second. Its symbol is Mio/s. It is the unit that disc benchmarks, copy tools and backup programs report in, and one of the few binary units most people see regularly without noticing.
Storage measurement produces it naturally. A benchmark writes and reads blocks whose size is a power of two, times the operation, and divides. The result is a binary rate, and reporting it as such preserves the arithmetic. A tool that converted to decimal megaoctets would introduce a 4.9 per cent adjustment for no purpose other than to match a marketing convention.
That five per cent is exactly where the two conventions diverge visibly for consumers. A drive advertised at 550 megaoctets per second and measured at 524 mebioctets per second is performing precisely as claimed; the numbers differ only because one is decimal and the other binary. A great deal of complaint about storage performance is this arithmetic misread as a shortfall.
For everyday sizes, one mebioctet per second copies a photograph in three seconds and a two-gigaoctet film in about half an hour. Modern drives run hundreds or thousands of times faster, so the unit is now the resolution at which small differences are reported rather than the scale of the whole figure.
The unit also appears in memory and cache measurements, in database throughput reports and in the output of the low-level commands that write disc images. All of these count in binary blocks because the underlying structures are binary, and all of them report in mebioctets per second because that is what the count divided by the time actually gives.
The habit of writing the lowercase i is worth keeping. It costs one character and it tells a later reader which of two conventions produced the number, which is information that cannot be recovered from context once it has been left out.
One mebioctet per second equals 1,048,576 octets per second, 1,024 kibioctets per second, or about 1.049 megaoctets per second.