Gigabyte per second to Mebibit per second

CPUs constantly shuttle data between RAM and their caches. DDR5-6000 provides about 96 GB/s of bandwidth in dual-channel mode. In games, insufficient RAM bandwidth causes frame drops during complex scenes. In productivity tasks like video encoding, it directly limits how fast the CPU can process data.

Thunderbolt 4 runs at 40 Gbps, which is 5 GB/s. Thunderbolt 5, released in 2024, doubles this to 80 Gbps (10 GB/s) with a burst mode up to 120 Gbps (15 GB/s). This is fast enough to run an external NVMe SSD at near-internal speeds.

Both, depending on generation. A PCIe 3.0 ×4 interface caps at ~3.5 GB/s, bottlenecking modern NAND. PCIe 4.0 ×4 raises this to ~7 GB/s, and PCIe 5.0 ×4 to ~14 GB/s. The drive's NAND flash and controller also have limits — the fastest SSDs and the fastest interfaces are in a constant leapfrog.

GPUs use wide memory buses (256–384 bits) with very fast HBM or GDDR6X memory running at high clock speeds. An RTX 4090 has a 384-bit bus with GDDR6X at 21 Gbps per pin, totalling 1,008 GB/s. HBM3 in data center GPUs achieves 3,000+ GB/s through stacked memory with 4096-bit buses.

At multi-GB/s rates, CPU processing speed, software efficiency, and thermal throttling become bottlenecks. A 14 GB/s PCIe 5.0 SSD can deliver data faster than most applications can consume it. Decompression, parsing, and memory allocation in software often cannot keep up with raw storage bandwidth.

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.