Terabit to Block

One terabit per second (Tbps) equals 125 gigabytes per second — enough to transfer the entire contents of a 1 TB hard drive in about 8 seconds. At this speed, you could download the entire Netflix library (estimated at around 100 petabytes) in roughly 800,000 seconds, or about 9 days.

Submarine fiber optic cables (such as the transatlantic cables connecting Europe and the Americas), long-haul terrestrial fiber routes, and the internal switching fabric of the largest hyperscale cloud data centers (Google, Amazon, Microsoft) operate at terabit and multi-terabit speeds. These use wavelength-division multiplexing (WDM) to carry many 100 Gbps or 400 Gbps channels on a single fiber.

Not in the foreseeable future for a single household connection. Current consumer endpoints (laptops, phones, TVs) cannot process or use data at terabit speeds — Wi-Fi 7 tops out around 46 Gbps theoretically. Terabit access would require new hardware at every endpoint. The practical benefit would be minimal since content servers themselves are not yet able to deliver at terabit rates to a single user.

Global internet traffic is measured in exabytes per month. Estimates suggest the internet backbone carries over 1,000 Tbps (1 Pbps) in aggregate during peak hours. Major internet exchange points (IXPs) like DE-CIX in Frankfurt regularly see peak traffic above 10 Tbps, and the largest cloud providers' internal networks operate at multi-petabit scales.

Current 5G mmWave cells can deliver up to 10–20 Gbps aggregate capacity shared among users in a sector. Industry roadmaps for 6G (targeted around 2030) aim for 1 Tbps aggregate throughput per cell site using sub-terahertz frequencies (100–300 GHz), massive MIMO antenna arrays, and intelligent reflecting surfaces. Achieving terabit wireless capacity requires extremely dense small-cell deployments — potentially one access point every 50–100 meters in urban areas.

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.