Kilobit to Block

The iconic dial-up handshake screech was a negotiation protocol between two modems. The initial tones tested line quality; the harsh noise burst was both modems rapidly cycling through modulation schemes (V.34, V.90) to find the fastest reliable speed — typically 28.8–56 kb/s. The sounds encoded training sequences, equaliser coefficients, and error-correction parameters, all transmitted as audio tones over a voice telephone line designed for 3.4 kHz bandwidth. The entire handshake lasted 10–30 seconds and transferred only a few kilobits of control data before the connection went silent for actual data transfer.

128 kb/s is considered acceptable quality for casual listening; 192–256 kb/s is a good balance of quality and file size; 320 kb/s is the maximum MP3 bitrate and is near-indistinguishable from lossless for most listeners. At 128 kb/s, one hour of audio is roughly 57 MB; at 320 kb/s, the same hour is about 144 MB.

No. A kilobit (kb) = 1,000 bits (SI, decimal). A kibibit (Kibit) = 1,024 bits (IEC, binary). The difference is small at this scale (2.4%) but compounds into significant gaps at larger prefixes. Network and telecom equipment use decimal kilobits; some older computing hardware documentation may use the binary definition.

The fastest consumer dial-up modems reached 56 kb/s (V.90 / V.92 standard), though practical speeds were often 40–50 kb/s due to line quality. At 56 kb/s, downloading a 5 MB MP3 file took about 12 minutes. By comparison, a modern 100 Mbps broadband connection is roughly 1,800 times faster.

Common audio bitrates: voice calls use 8–64 kb/s (G.711 codec = 64 kb/s); AAC audio at 96–256 kb/s; MP3 at 128–320 kb/s; lossless FLAC at 700–1,400 kb/s depending on audio content. Streaming services like Spotify use 24 kb/s (low) to 320 kb/s (premium) for music delivery.

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.