Block to Bit

Modern hard drives (2011+) and SSDs use 4,096-byte (4 KiB) physical sectors — known as "Advanced Format" or AF. Legacy drives used 512-byte sectors. Filesystems (NTFS, ext4, APFS) typically use 4 KiB logical block sizes to match physical sectors, which avoids the performance penalty of misaligned writes. Enterprise SSDs may use larger block sizes (16 KiB or more) for better parallelism.

Cloud block storage services (AWS EBS, Azure Managed Disks, GCP Persistent Disk) use I/O block sizes typically of 4 KiB or 16 KiB. Performance is measured in IOPS (I/O operations per second) and throughput (MB/s) — both depend on block size. A throughput-optimized workload (sequential video) benefits from large blocks; an IOPS-optimized workload (database random reads) uses small blocks.

Filesystems allocate disk space in whole blocks. On a system with 4 KiB blocks, every file — no matter how small — occupies at least 4,096 bytes. A directory of 10,000 small configuration files (each 100 bytes of content) uses 40 MB of disk space (10,000 × 4,096 bytes) rather than 1 MB (10,000 × 100 bytes). This is called "block slack" or "internal fragmentation".

Disk blocks (filesystem blocks) are typically 512 bytes to 4 KiB. Database blocks (database pages) are the unit of I/O for a database engine — typically 8 KiB (PostgreSQL, SQL Server), 16 KiB (MySQL InnoDB), or 32 KiB (Oracle, configurable). Database blocks usually align to multiples of disk blocks for efficiency. Reading one database page may involve reading 2–8 disk blocks.

RAID stripe size (or chunk size) is the amount of data written to each drive before moving to the next drive in the array — typically 64 KiB to 512 KiB. It should be set to match your workload: sequential large-file workloads benefit from larger stripe sizes; random small-block workloads benefit from stripe sizes closer to the filesystem block size. Mismatched stripe and block sizes cause write amplification and reduce RAID performance.

A bit is a single binary value (0 or 1); a byte is a group of 8 bits. Bytes are the standard unit for file sizes, memory, and storage. Network speeds are typically quoted in bits per second (Mbps), while file sizes use bytes (MB) — so a 100 Mbps connection downloads 100 megabits, or about 12.5 megabytes, per second.

Networking hardware physically transmits one bit at a time over a wire or radio signal, so bits per second is the natural unit for measuring throughput. The convention predates widespread file-size awareness. When you see "100 Mbps broadband", your actual download speed in MB/s is about 1/8 of that — roughly 12.5 MB/s.

A classical bit is definitively 0 or 1. A qubit can exist in a superposition of both states simultaneously, described by two complex probability amplitudes. When measured, a qubit collapses to 0 or 1 — yielding one classical bit of information. The power of qubits lies in entanglement and interference during computation, not in storing more data per unit. A 100-qubit quantum computer does not store 100 bits more efficiently; it explores 2¹⁰⁰ computational paths in parallel for specific algorithm types like factoring and search.

Information theory, developed by Claude Shannon in 1948, quantifies how much information a message contains. One bit is the amount of information needed to resolve a choice between two equally likely outcomes. This abstraction underpins all digital compression, encryption, and error-correction — from MP3 audio to HTTPS security.

In practice, modern computers cannot address or store a single bit individually — the minimum addressable unit is one byte (8 bits). Trying to store a single bit requires a full byte, with 7 bits unused. Some specialised hardware and bit-packing algorithms can store multiple boolean values per byte, but standard memory hardware works at byte granularity.