Nibble to Petabit

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.

One petabit = 10¹⁵ bits = 125 terabytes. To put it in perspective: the entire text content of all English Wikipedia articles is roughly 4 GB — so a petabit could hold about 31,000 copies of it. A petabit per second link could transfer all of Wikipedia's text content in about 32 microseconds.

As of 2024, no single commercial link carries 1 Pbps, but laboratory experiments have demonstrated fiber optic transmission exceeding 1 Pbps using dense wavelength-division multiplexing on a single fiber strand. Commercial submarine cables aggregate hundreds of terabits per second across many fibers and wavelengths, collectively reaching petabit-scale capacity per cable system.

A petabit (Pb) = 10¹⁵ bits. A petabyte (PB) = 10¹⁵ bytes = 8 petabits. Storage systems (data centers, archival systems) use petabytes for capacity; aggregate network throughput uses petabits per second. An exabyte-scale data center stores 1,000 petabytes; its internal network may carry multiple petabits per second of traffic.

Qubits and classical bits solve fundamentally different problems — qubits will not simply replace petabit-scale classical storage or networking. A quantum computer with 1,000 logical qubits can explore 2¹⁰⁰⁰ states simultaneously, but measuring those qubits collapses them to classical bits. Quantum networks will likely handle key distribution and entanglement sharing at kilobit-to-megabit rates, while classical infrastructure continues to move petabits of bulk data. The two technologies are complementary, not substitutional.

Submarine fiber optic cables are built by a handful of companies (SubCom, NEC, Alcatel Submarine Networks) and typically cost $200–500 million per system. A modern cable contains 12–24 fiber pairs, each carrying hundreds of wavelengths via dense wavelength-division multiplexing, reaching 400+ Tbps aggregate capacity per cable. Cables are designed to last 25 years on the ocean floor. When faults occur, specialised cable repair ships (fewer than 60 exist worldwide) locate breaks using optical time-domain reflectometry and splice repairs at sea — a process that can take days to weeks depending on depth and weather.