Kilobyte per second to Gibibit per second

A typical 4 MB MP3 file at 7 kB/s took about 9–10 minutes to download. Napster users in 1999 would queue up songs before bed and hope the phone line stayed connected overnight. A single disconnection meant starting over from scratch.

Lowercase "k" with uppercase "B" (kB/s) means 1,000 bytes per second (SI decimal). Uppercase "K" with uppercase "B" (KB/s) traditionally meant 1,024 bytes per second (binary). In practice, most software uses them interchangeably, and the difference is only 2.4%.

Apps display kB/s when transfer speeds are genuinely that slow — downloading over congested mobile networks, tethering in rural areas, or transferring tiny files where the connection never ramps up. It is also common in SSH/SCP transfers that display instantaneous speed during small file copies.

The first consumer ADSL plans offered 256 kbps downstream, delivering about 32 kB/s — roughly 4.5× faster than a 56k modem. A 512 kbps plan gave 64 kB/s. That first jump from 7 to 32 kB/s felt revolutionary, cutting a 10-minute download to about 2 minutes.

An SMS is limited to 140 bytes (160 characters in GSM-7 encoding), and the signalling channel transmits it almost instantly. But if you think of SMS throughput over a sustained period, the practical rate is about 0.1–0.5 kB/s because of the overhead between messages.

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.