Megabyte per second to Gibibit per second

Many USB drives use a small SLC cache for initial writes at high MB/s, then slow dramatically once the cache fills and data writes to slower TLC/QLC NAND. A drive that starts at 200 MB/s might drop to 20–30 MB/s after the first few gigabytes. Check sustained write speed reviews, not just peak numbers.

Editing 4K ProRes footage requires about 200–400 MB/s of sustained read speed. 8K RAW can demand 1,000+ MB/s. A SATA SSD (550 MB/s) handles 4K fine, but 8K workflows really need NVMe drives at 3,000+ MB/s. The timeline scrubbing experience directly correlates with MB/s.

Look at the capitalisation: lowercase "b" (Mbps) means megabits, uppercase "B" (MB/s) means megabytes. Most speed test websites (Speedtest by Ookla, fast.com) default to Mbps. If your result seems 8× lower than expected, you are probably reading MB/s where you expected Mbps.

PCIe 5.0 NVMe SSDs hit 12,000–14,000 MB/s sequential read speeds. That is fast enough to load an entire 50 GB game in about 4 seconds. PCIe 6.0 drives, expected soon, will double this again to roughly 25,000 MB/s.

Network transfers add latency, protocol overhead (SMB, NFS), and are limited by the network link speed. A file on a local NVMe SSD reads at 7,000 MB/s, but sharing it over a 1 Gbps network caps throughput at 125 MB/s. Even 10 GbE only gives 1,250 MB/s — a fraction of modern SSD capability.

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.