Gibibit per second to Mebibit per second

At gibibit speeds, 7.4% represents a substantial amount of data. The difference between 10 Gibps and 10 Gbps is 737 Mbps — enough bandwidth for several 4K video streams. When designing storage fabrics or HPC interconnects, misinterpreting the unit can lead to underprovisioned systems.

PCIe specifications are actually defined in GT/s (gigatransfers per second) with specific encoding overhead. PCIe 3.0 uses 128b/130b encoding at 8 GT/s, giving about 985 MB/s per lane — which is closer to binary GiB/s than decimal GB/s. The industry uses both units somewhat loosely.

InfiniBand specifications use decimal rates (HDR = 200 Gbps, NDR = 400 Gbps per port). However, some HPC benchmarks and documentation convert to binary units for consistency with memory bandwidth figures. Always check the document's unit convention to avoid the 7% discrepancy.

Ordering a 100 Gibps fabric when you needed 100 Gbps means overpaying for 7.4% more bandwidth than necessary. Conversely, provisioning 100 Gbps when your workload needs 100 Gibps leaves you 7.4% short, potentially causing congestion during peak loads. At data center scale, these margins translate to real money.

Unlikely. Networking is firmly decimal (Ethernet, fiber optics), while memory and storage have binary roots. The two worlds overlap in storage networking, causing permanent confusion. The best practice is to always explicitly state "decimal" or "binary" in specifications rather than hoping everyone agrees.

Mainly in Linux system tools, IEC-compliant technical specifications, and some enterprise storage documentation. The iperf3 network testing tool can report in Mibps if configured to use binary units. Most consumer-facing software and ISPs use megabits exclusively.

Multiply by 1.048576. So 100 Mibps = 104.86 Mbps. To go from Mbps to Mibps, divide by 1.048576. At small values the difference is negligible, but at gigabit scales it can mean a meaningful amount of data.

Linux kernel developers historically followed IEC recommendations to use binary prefixes where applicable. Some tools like dd and rsync default to binary (MiB/s) for disk operations. However, network-facing tools like ethtool and ip still use decimal Mbps because that is what the hardware reports.

For casual use, no. For capacity planning and SLA compliance, yes. If a contract guarantees 100 Mibps and the provider measures in Mbps, the customer might get 100 Mbps (only 95.4 Mibps) and technically be short-changed. Data center SLAs should specify which unit system applies.

No — ISPs legitimately use decimal megabits because Ethernet and fiber standards are decimal. A "100 Mbps" plan genuinely delivers 100,000,000 bits per second. The confusion arises only when comparing with binary-unit tools. ISPs are not hiding anything; the two systems just coexist awkwardly.