Gigabit to Mebibyte

1 Gbps (gigabit) broadband delivers up to 125 MB/s, which is more than sufficient for most households. It supports dozens of simultaneous 4K streams, fast game downloads, and video conferencing with headroom to spare. The limiting factor is usually the Wi-Fi router (Wi-Fi 5 maxes out around 400–600 Mbps in practice) or the speed of the remote server you're downloading from.

10 Gbps networking is standard in data centers, server interconnects, and high-performance workstations doing large file transfers (video editing, database backups). It is increasingly available in prosumer home networking equipment. At 10 Gbps, a 1 TB file transfer takes about 13 minutes under ideal conditions.

One terabit equals 1,000 gigabits (SI). Terabit-per-second (Tbps) speeds are used in long-haul fiber optic cables and internet backbone infrastructure. A single transatlantic fiber cable typically carries hundreds of terabits per second across many multiplexed channels.

Wi-Fi 5 (802.11ac) delivers up to 3.5 Gbps theoretical, but typically 400–600 Mbps real-world on a single device. Wi-Fi 6 (802.11ax) reaches 9.6 Gbps theoretical and 600–900 Mbps practical per device, with better multi-device handling via OFDMA. Wi-Fi 6E extends the same technology into the uncongested 6 GHz band, improving real-world speeds to 1–2 Gbps. Wi-Fi 7 (802.11be) pushes the theoretical maximum to 46 Gbps using 320 MHz channels and 4096-QAM, with real-world single-device speeds expected around 2–5 Gbps — the first Wi-Fi standard to reliably exceed gigabit in practice.

Modern data centers handle enormous simultaneous traffic between thousands of servers — cloud computing, video streaming, and AI training all require massive internal bandwidth. 100 Gbps links between switches are now standard; 400 Gbps is increasingly deployed for spine connections. At these speeds, a single link can move 50 GB of data per second, keeping pace with NVMe storage arrays and GPU memory transfer rates.

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). MiB is 4.86% larger. This gap is why a file manager on Linux showing "512 MiB" of free RAM and a marketing sheet showing "512 MB" of RAM are technically different: the marketing sheet refers to fewer bytes.

The original CD-ROM standard defined capacity as 74 minutes of audio or 650,000,000 bytes. Technically this is 650 MB in SI terms, or approximately 620 MiB (since 650,000,000 ÷ 1,048,576 ≈ 620). However, the CD industry loosely used "MB" to mean 650 × 10⁶ bytes. Some media used 700 MB (≈ 668 MiB). This inconsistency is a classic example of the pre-IEC ambiguity.

Docker reports image sizes in decimal MB (e.g., "docker images" shows 150 MB), but the underlying layer storage on disk uses binary-aligned block sizes. A "150 MB" Docker image actually occupies roughly 143 MiB on disk before compression. Compressed layers further complicate things: a 150 MB uncompressed image might only transfer 50 MB over the network. Container registries like Docker Hub display compressed sizes, while "docker images" shows uncompressed — leading to frequent confusion in CI/CD pipeline size budgets.

One mebibyte (1,048,576 bytes) holds about: one minute of MP3 audio at 128 kbps (≈ 960 kB, so slightly under 1 MiB), a medium-resolution JPEG photo (0.5–2 MiB), about 200 pages of plain text, or the complete text of a short novel. A typical Linux kernel image at boot is 8–12 MiB compressed.

RAM chips are physically organized as binary address grids — each address line doubles the capacity, so sizes must be exact powers of 2 (4 GiB = 2³² bytes, 8 GiB = 2³³ bytes). USB flash drives use NAND flash that is also binary internally, but manufacturers reserve variable amounts for wear levelling, bad block management, and controller firmware. A "64 GB" USB drive might have 64 GiB of raw NAND but only expose 59.6 GiB (64 × 10⁹ ÷ 2³⁰) to the user — the label uses decimal marketing, unlike RAM which honestly reflects binary sizing.