Gibibyte to Exabit

GB (gigabyte) = 10⁹ bytes = 1,000,000,000 bytes (SI decimal). GiB (gibibyte) = 2³⁰ bytes = 1,073,741,824 bytes (IEC binary). GiB is 7.37% larger. This is why a 1 TB hard drive labelled by the manufacturer (using 10¹² bytes) appears as approximately 931 GiB in Windows or Linux (which divide by 1,073,741,824). Neither value is wrong; they use different counting systems.

Early PC games (1990s) fit on a few floppy disks — under 10 MiB. CD-era games (late 1990s) reached 650 MiB. DVD-era titles hit 4–8 GiB. Modern AAA games like Call of Duty or Flight Simulator now exceed 100–200 GiB due to uncompressed 4K textures, high-fidelity audio in multiple languages, and pre-rendered cinematics. The growth rate has outpaced Moore's Law: storage needs roughly double every 2–3 years for top-tier games, driven primarily by texture resolution increases that scale quadratically with pixel count.

A module sold as "16 GB" RAM by manufacturers means 16 × 10⁹ = 16,000,000,000 bytes? No — RAM is actually built in binary powers. A "16 GB" RAM module contains exactly 2³⁴ = 17,179,869,184 bytes = 16 GiB. In this case, the manufacturer is using "GB" to mean GiB — unlike hard drives, where manufacturers genuinely use decimal GB. RAM capacities are always powers of 2 in gibibytes.

A 512 GB SSD (decimal, as labelled by the manufacturer) holds 512,000,000,000 bytes. Divide by 1,073,741,824 to get GiB: 512,000,000,000 ÷ 1,073,741,824 ≈ 476.8 GiB. After OS overhead and firmware reserved space, the usable capacity shown in the OS is typically 450–465 GiB for a nominally 512 GB drive.

Yes — GiB is the technically correct unit for binary memory. RAM, CPU cache, and GPU memory are all physically organized in powers of 2, making GiB the natural unit. The JEDEC memory standard (the body that defines RAM specifications) officially uses the IEC GiB notation, even though product packaging often says "GB" for commercial reasons. In engineering and OS development contexts, GiB is the preferred term.

One exabit = 10¹⁸ bits = 125,000 terabytes = 125 petabytes. If every person on Earth (8 billion people) each stored 15 GB of data — roughly a modern smartphone's photos and messages — the total would be about 120 exabytes, or about 960 exabits. The entire human genome is about 1.5 GB; sequencing every person on Earth would produce about 12 exabytes of data.

Cisco's annual internet traffic reports estimated global IP traffic at roughly 4.8 exabytes per day in 2022, rising about 20% per year. Expressed in bits, that's about 38 exabits per day or roughly 440 petabits per second continuously. Video streaming accounts for over 60% of total internet traffic volume.

Data gravity is the principle that massive datasets attract applications, services, and additional data toward them — rather than being moved to where processing occurs. At exabit scale, physically transferring data becomes impractical: moving 1 exabit over a 100 Gbps link takes 116 days. Instead, companies deploy compute resources alongside the data. This effect drives cloud concentration — once an organisation stores exabits in AWS or Azure, the cost and latency of moving that data elsewhere creates powerful vendor lock-in, shaping the economics of the entire cloud industry.

The Square Kilometer Array (SKA), under construction in Australia and South Africa, will be the world's largest radio telescope. Its thousands of antennas will collectively produce roughly 1 exabit of raw sensor data per day — more than the entire global internet traffic of the early 2000s. This data cannot be stored in full; instead, on-site supercomputers reduce it by a factor of ~10,000 in real time, keeping only scientifically relevant signals. The SKA illustrates how radio astronomy pushes data processing to extreme scales that rival commercial internet infrastructure.

At 1 Gbps (a fast home connection), downloading 1 exabit would take 1 billion seconds — about 31.7 years. At 1 Tbps (a high-end data center link), it would take 1 million seconds, or about 11.6 days. This illustrates why exabit-scale data movements require massively parallel infrastructure — no single link or device handles exabit transfers directly.