Gibibyte per second to Mebibit per second

GPU memory is addressed in binary (power-of-2 bus widths like 256-bit or 384-bit), so binary units naturally describe the actual hardware capability. Some vendors use GiB/s to be precise, while marketing materials prefer the larger-sounding GB/s number. The RTX 4090's 1,008 GiB/s is 1,082 GB/s — the latter sounds faster.

DDR5-6000 in dual-channel mode provides about 93 GiB/s (100 GB/s). Quad-channel DDR5 on workstation platforms doubles this to ~186 GiB/s. The actual usable bandwidth depends on memory access patterns — random access achieves far less than sequential streaming.

Memory bandwidth (50–100+ GiB/s for DDR5) measures how fast the CPU can read/write RAM. Storage bandwidth (3–14 GiB/s for NVMe SSDs) measures persistent data transfer. Memory is 10–30× faster because DRAM has nanosecond latency while NAND flash has microsecond latency. They serve different roles in the data hierarchy.

Yes. For memory bandwidth, run a STREAM benchmark (available for Linux and Windows). For storage, use fio or CrystalDiskMark. GPU memory bandwidth can be tested with gpu-burn or vendor-provided tools. All will report in either GiB/s or GB/s depending on the tool — check which one.

Electrical signalling on copper traces maxes out around 112 Gbps (about 13 GiB/s) per lane with current technology. Beyond that, optics take over — silicon photonics interconnects can push individual channels to 200+ Gbps. The physical speed of light in fiber is not the limit; it is the modulation and detection electronics.

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.