| Mebioctets per second (Mio/s) | Kibibits per second (Kibit/s) |
|---|---|
| 1 Mebioctet per second | 8192 Kibit/s |
| 2 Mebioctets per second | 16384 Kibit/s |
| 3 Mebioctets per second | 24576 Kibit/s |
| 4 Mebioctets per second | 32768 Kibit/s |
| 5 Mebioctets per second | 40960 Kibit/s |
| 10 Mebioctets per second | 81920 Kibit/s |
| 20 Mebioctets per second | 163840 Kibit/s |
| 25 Mebioctets per second | 204800 Kibit/s |
| 50 Mebioctets per second | 409600 Kibit/s |
| 100 Mebioctets per second | 819200 Kibit/s |
| Reference | Mebioctets per second (Mio/s) | Kibibits per second (Kibit/s) |
|---|---|---|
| A dial-up modem | 0.00667572 Mio/s | 54.6875 Kibit/s |
| Typical home broadband | 11.9209 Mio/s | 97656.2 Kibit/s |
| Gigabit Ethernet | 119.209 Mio/s | 976562 Kibit/s |
| Streaming a 4K film | 2.98023 Mio/s | 24414.1 Kibit/s |
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.
The kibibit per second is a unit of data transfer rate equal to 1,024 bits per second. Its symbol is Kibit/s. It is the binary counterpart of the kilobit per second, and it is the least used member of an already unusual family, because transfer rates are one of the few places in computing where the decimal convention has always been unambiguous.
Networking has counted in true thousands from the beginning. A modem rated at 56 kilobits per second meant fifty-six thousand, not fifty-seven thousand three hundred and forty-four. The reason is that a transmission rate is set by a clock, and clocks are specified in decimal frequencies: a link running at ten million symbols per second carries a decimal number of bits, not a power of two.
The binary prefixes exist for quantities, not for rates, because quantities of storage are organised in powers of two while time is not. There is no natural reason for a rate to be a power of two, and consequently no reason for a rate unit to need a binary prefix. Where one appears, it is almost always because a program divided a binary file size by a duration.
That is exactly where the kibibit per second does turn up. A tool that measures a transfer by counting kibioctets and dividing by seconds produces a rate in kibioctets per second, and multiplying by eight gives kibibits per second. The unit is a consequence of the arithmetic rather than a description of the channel.
For scale, a kibibit per second is 128 octets per second, and the difference from a kilobit per second is 2.4 per cent — smaller than the measurement error of almost any real throughput test. At this level the distinction is technically correct and practically invisible, which is a fair description of the whole binary prefix system at its lower end.
The unit is properly defined and a converter must handle it, because the IEC series applies to every unit without exception. Whether anyone writes it is a separate question from whether it means something definite, and it does.
One kibibit per second equals 1,024 bits per second, 128 octets per second, or 1.024 kilobits per second.