Kibibit per second to Gibibit per second

Because "kilo" was used to mean both 1,000 and 1,024 depending on context, causing real confusion. RAM manufacturers used 1,024 (binary) while network engineers used 1,000 (decimal). The IEC created kibi (Ki) in 1998 to unambiguously mean 1,024, leaving kilo for exactly 1,000.

Very few people outside of standards bodies and kernel developers. Linux kernel networking code sometimes uses binary units internally, and some IEC-compliant technical documents use Kibps. But consumer networking has fully standardized on decimal kilobits (kbps), making kibibits a niche pedantic distinction.

At the kibi/kilo level, only 2.4%. But the gap compounds — mebi vs mega is 4.86%, gibi vs giga is 7.37%, and tebi vs tera is 9.95%. A "1 TB" hard drive holds only 931 GiB in binary terms, which is why your new drive looks smaller than advertised in Windows.

Hard drives are built from sectors of arbitrary size, so decimal marketing (1 TB = 1,000 GB) is natural and makes drives look bigger. RAM is addressed in powers of 2 because of how binary memory chips work, so binary units (GiB) reflect actual hardware architecture. Neither side wants to change.

Almost certainly not. Networking adopted decimal (×1000) from the beginning because serial link speeds are clock-derived and have nothing to do with powers of 2. Ethernet has always been 10/100/1000 Mbps. Binary prefixes solve a storage problem that networking never had.

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.