Data Transmission
At Layer 1, data is just physics. It’s voltage on copper, light in fiber, or waves in the air. Understanding these physical constraints is critical for debugging performance issues, as they define the absolute limits of how fast and how much data you can move between two points.
1. Duplexing (Direction of Flow)
Before data can flow, the network must agree on how devices share the medium. This is known as duplexing.
| Type | Direction | Hardware Reality | Example |
|---|---|---|---|
| Simplex | One way only. | A single dedicated transmission line without a return path. | TV Broadcast, Pagers, GPS signals. |
| Half-Duplex | Both ways, but one at a time. | Devices share the same frequency or physical wire. Requires collision avoidance (like CSMA/CD). | Walkie-Talkie, early Ethernet hubs, Wi-Fi (802.11). |
| Full-Duplex | Both ways, simultaneously. | Independent send and receive channels (e.g., separate twisted pairs or fiber strands). | Modern Switched Ethernet, Telephone calls, Fiber Optics. |
[!NOTE] The Wi-Fi Reality Despite feeling “Full-Duplex” to users, Wi-Fi operates in Half-Duplex. Only one device can transmit on a given channel at a time. This is why crowded coffee shop Wi-Fi feels slow—devices are politely taking turns talking to the router, waiting for “airtime.”
2. Bandwidth vs Throughput vs Goodput
There is a critical difference between the theoretical “Pipe Size” and the “Water Flow” that actually reaches the destination.
- Bandwidth: The Maximum theoretical data rate determined by physical signaling capabilities (e.g., a 1 Gbps Ethernet link). Think of this as the width of the highway—how many lanes exist.
- Throughput: The Actual rate of successful data delivery over the medium. Think of this as the speed of traffic.
- Throughput < Bandwidth due to protocol overhead (Headers), medium contention, packet loss, and network congestion.
- Goodput: The amount of useful Application-layer Data delivered per second (excluding all headers, retransmissions, and control frames). If you download a 100 MB file, Goodput measures how fast the file itself arrived.
The Anatomy of a Transfer
Imagine sending a 10 MB image over a 100 Mbps link:
- Application Data (Goodput): The pure 10 MB payload.
- Protocol Overhead (Throughput): TCP, IP, and Ethernet headers add roughly 5-10% overhead to wrap the payload.
- Physical Link (Bandwidth): The 100 Mbps copper wire physically sending the signals.
[!TIP] Mnemonic: The Water Pipe
- Bandwidth: The diameter of the pipe.
- Throughput: The amount of water currently flowing through it (might not be full).
- Goodput: The amount of clean, drinkable water that reaches your glass (minus leaks and mud).
[!NOTE] Bandwidth-Delay Product (BDP)
BDP = Bandwidth * RTT. This calculates the amount of data “in flight” on the wire at any given moment. If you have a 1Gbps link with 100ms latency, you need100,000,000 bits(about 12.5 MB) of buffer space to fill the pipe. If TCP window sizes are smaller than the BDP, the network is underutilized.
3. The 4 Types of Latency
“Lag” is not a single monolith; it’s the mathematical sum of four distinct delays that occur as a packet journeys from source to destination.
1. Processing Delay
The time it takes for a router or switch CPU to read the packet header, check routing tables, and decide where to send it.
- Scale: Usually negligible (microseconds).
- Hardware Reality: Handled by specialized ASICs in modern enterprise routers to process millions of packets per second.
2. Queuing Delay
The time a packet spends sitting in a router’s buffer waiting for its turn to be transmitted.
- Scale: Highly variable (milliseconds to seconds).
- Hardware Reality: Driven by network congestion. If packets arrive faster than they can be transmitted, the queue grows. If the queue is full, packets are dropped (Packet Loss).
3. Transmission Delay
The time required to push all the bits of a packet onto the physical wire.
- Formula:
Delay = Packet Size / Bandwidth - Scale: Dependent on link speed.
- Example: Pushing a 1500-byte packet onto a 10 Mbps link takes
1.2 ms. Pushing it onto a 1 Gbps link takes0.012 ms. - Faster Link = Lower Transmission Delay.
4. Propagation Delay
The time it takes for a single bit to physically travel from the start of the wire to the end.
- Formula:
Delay = Distance / Propagation Speed(Speed of light in the medium) - Scale: Dictated by the laws of physics. Light in a fiber-optic cable travels at roughly
200,000 km/s(about 2/3 the speed of light in a vacuum). - Example: Traveling from New York to London (~5,500 km) takes at least
27.5 msof pure propagation delay. - Shorter Cable = Lower Propagation Delay. Upgrading bandwidth does nothing to improve propagation delay!
4. Interactive: Latency Calculator
Experiment with the physics of data transmission to see how bandwidth affects transmission delay, while distance strictly governs propagation delay.
- Packet Size: Standard Ethernet MTU is 1500 Bytes. Jumbo frames can be 9000 Bytes.
- Bandwidth: 1 Mbps (Slow DSL) up to 1000 Mbps (Gigabit Fiber).
- Distance: 100km (Inter-city) vs 5000km (Trans-Atlantic).