Pebibyte to Nibble

PB (petabyte) = 10¹⁵ bytes = 1,000,000,000,000,000 bytes (SI decimal). PiB (pebibyte) = 2⁵⁰ bytes = 1,125,899,906,842,624 bytes (IEC binary). PiB is 12.59% larger. For a data center purchasing 100 PiB of raw storage, the SI vs IEC confusion would represent approximately 12.59 PB of missing or unexpected capacity.

Cloud providers (AWS, Azure, GCP) operate at exabyte scale but provision and bill individual customers at PiB scale for enterprise storage. Scientific computing facilities like CERN, the Square Kilometer Array telescope project, and US national laboratories store tens to hundreds of PiB. Large video platforms (Netflix, YouTube) store hundreds of PiB of encoded video content.

Using 20 TB drives (a 2024 high-density consumer drive): 1 PiB = 1,125,899,906,842,624 bytes ÷ 20,000,000,000,000 bytes/drive ≈ 56.3 drives. So roughly 57 × 20 TB drives to fill 1 PiB. In a data center using 60-drive storage shelves, one shelf of 60 × 20 TB drives provides about 1.07 PiB of raw capacity.

Magnetic tape (LTO technology) remains the dominant medium for cold storage at PiB scale due to economics and durability. An LTO-9 cartridge holds 18 TB (uncompressed) and costs roughly $100 — about $5.50 per TB, versus $15–20 per TB for HDDs. Tape also consumes zero power when idle, unlike spinning disks. The IBM TS4500 tape library can hold over 40 PiB in a single rack. Major users include CERN, national archives, and film studios — Netflix stores its master copies on tape. Tape's main downside is sequential access: retrieving a specific file can take minutes versus milliseconds for disk.

CERN's Worldwide LHC Computing Grid stores approximately 300–400 PB (petabytes, decimal) of data across distributed sites, with the main Tier-0 facility at CERN holding about 100 PB on disk and 200 PB on tape. The LHC generates roughly 15 PB of data per year from collision events. Future upgrades (High-Luminosity LHC) are projected to increase this to 50–100 PB per year.

A nibble is 4 bits, or half a byte. It encodes one hexadecimal digit (values 0–15, represented as 0–9 and A–F). Nibbles are important in BCD (binary-coded decimal) encoding, where decimal digits are packed two per byte (each digit occupying one nibble). Packed BCD is used in financial systems and legacy databases to represent decimal numbers without floating-point rounding errors.

Hexadecimal (base 16) maps perfectly to nibbles because 4 bits can represent exactly 16 values (2⁴ = 16). One byte = two nibbles = two hex digits. A byte value of 0xFF (255 in decimal) is two nibbles: F (1111) and F (1111). This mapping makes hexadecimal the natural notation for expressing binary data — programrs use hex because one hex digit always represents a fixed number of bits.

Binary-Coded Decimal (BCD) encodes each decimal digit (0–9) as a 4-bit binary value (nibble). Two decimal digits fit in one byte using "packed BCD". For example, the decimal number 47 is stored as 0100 0111 in packed BCD — each nibble holds one digit. BCD avoids the rounding errors of binary floating-point, which is why it is used in financial software, calculators, and legacy banking systems.

A nibble = 4 bits (1 hex digit). A byte = 8 bits (2 hex digits, 2 nibbles). A word = typically 16, 32, or 64 bits depending on the processor architecture (see the "word" unit for details). These are the fundamental granularities of digital data: nibble for hex/BCD, byte for text and addressing, word for native processor arithmetic.

Nibbles are rarely referenced directly in modern high-level programming but remain fundamental at the hardware level. Embedded systems, FPGA design, network packet parsing, and hardware description languages (VHDL, Verilog) regularly manipulate nibbles. The nibble is also the key concept behind hexdump utilities — the canonical way to inspect raw binary files and network packets.