Conversion from Mebioctets per second to Pebibits per second

Information about the Mebioctet per second (Mio/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.

Information about the Pebibit per second (Pibit/s)

The pebibit per second is a unit of data transfer rate equal to 1,024 tebibits per second, which is two to the fiftieth power bits per second. Its symbol is Pibit/s. It is the binary counterpart of the petabit per second, and the two differ by 12.6 per cent.

No deployed system runs at this rate, and the unit therefore describes either an aggregate or a laboratory result. Optical transmission records set on single fibres reach a petabit per second, and the binary figure for the same experiment is 12.6 per cent lower — a difference that matters when comparing results between papers that use different conventions.

Where the unit is genuinely appropriate is in describing structures built from powers of two. The total switching capacity of a very large network fabric, built from ports and buffers that are all binary, is a binary quantity divided by time, and reporting it in decimal units discards the arithmetic that produced it. The same applies to the summed memory bandwidth of a machine whose channel count is a power of two.

In octets a pebibit per second is 140,737,488,355,328, which is 128 tebioctets per second. That is the storage of a thousand large consumer drives moved every second, and it exists only as a total across many thousands of parallel paths inside a single facility.

The size of the discrepancy at this level is the argument for the whole IEC series in miniature. What began as a harmless 2.4 per cent at the kibibit is now an eighth, and it compounds by 2.4 per cent at every further step. A convention that was acceptable for small numbers becomes untenable for large ones, and the point of the binary prefixes is to make the distinction visible before that happens.

For a converter, the arithmetic is unremarkable: multiply or divide by 1,024 the appropriate number of times, and by eight to reach octets. What matters is that the tool does not silently substitute the decimal unit when it sees a value it cannot label precisely.

One pebibit per second equals 1,024 tebibits per second, 140,737,488,355,328 octets per second, or about 1.126 petabits per second.