Gibibyte per second to Kibibyte 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.

Rsync follows IEC binary conventions because it deals with file sizes that are measured in binary units by the filesystem. Since files occupy whole filesystem blocks (typically 4 KiB), reporting transfer speed in KiB/s makes the math consistent with actual data moved on disk.

1 KiB/s (1,024 bytes/second) is 2.4% faster than 1 kB/s (1,000 bytes/second). The difference is tiny at this scale but matters when you are designing buffer sizes for embedded systems where every byte of RAM counts.

Microsoft started using binary units more consistently in Windows 10 after years of ambiguity where "KB" sometimes meant 1,000 and sometimes 1,024 bytes. The shift toward KiB follows IEC recommendations and reduces confusion, though the transition is still incomplete across all Windows tools.

A 3.5-inch floppy drive transferred data at about 31–62 KiB/s (250–500 kbps). Copying a full 1.44 MB floppy took roughly 25–50 seconds. For comparison, a modern NVMe SSD is about 100,000 times faster.

In embedded systems with tight memory constraints, confusing 1,024 with 1,000 can overflow a buffer. In network protocols, a spec written in KiB/s being implemented as kB/s means transmitting 2.4% less data than expected per second — enough to cause timing violations in real-time systems.