Simple explanation
When connectivity works but performance is poor, this lesson covers the specific metrics and causes behind "the network is slow."
Technical explanation
- Latency — the delay for data to travel from source to destination, often the actual root cause behind a vague "slow" complaint, distinct from throughput.
- Jitter — variation in latency over time, especially damaging for real-time traffic like voice/video, even when average latency looks acceptable.
- Packet loss — packets failing to arrive at all, forcing retransmission (for TCP) and directly degrading real-time traffic (for UDP-based voice/video, which typically doesn't retransmit).
- Bandwidth saturation — a link genuinely at or near its maximum capacity, a straightforward (if sometimes expensive to fix) cause.
- Bottlenecks — a single underperforming link or device constraining an otherwise capable network, often findable by checking utilization at each hop along a path.
- Broadcast storms — excessive broadcast traffic (often from a switching loop) consuming available bandwidth and device processing capacity.
- CPU/memory utilization on network devices — an overloaded router or switch can degrade performance even with plenty of raw link bandwidth available, since the device itself becomes the bottleneck processing traffic.
- QoS misconfiguration — even with sufficient overall bandwidth, poorly configured (or entirely absent) QoS can let latency-sensitive traffic suffer behind bulk transfers.
- Wireless-specific performance issues: channel congestion (too many networks/devices on the same channel), signal-to-noise ratio degradation, and client density exceeding what an AP can handle well.
Synonyms / related terms
| Term | Means | |---|---| | Jitter | Variation in latency over time | | Bottleneck | The single most-constraining point along a network path | | SNR | Signal-to-Noise Ratio, relevant to wireless performance |
Concept Check
"A VoIP call has acceptable average latency but sounds choppy and inconsistent, with words occasionally cutting out." Average latency alone doesn't explain this — the specific symptom (inconsistent, choppy audio despite acceptable average delay) points to jitter, the variation in latency, which is especially disruptive for real-time voice traffic even when the average number looks fine on paper.
Interview-style Q&A
Q: Why can a router with plenty of link bandwidth still cause a performance problem? A: "Bandwidth describes the capacity of the LINK, but the device itself still has to process every packet — if its CPU is maxed out from routing table lookups, ACL processing, or an overwhelming packet rate, it becomes the actual bottleneck regardless of how much raw bandwidth the physical link could theoretically carry. The symptom looks like a bandwidth problem, but the fix (device upgrade, offloading processing) is completely different."
Memory trick
"Latency is Delay, Jitter is Inconsistent Delay, Loss is Missing entirely" — three related-but-distinct performance metrics, each tied to a one-word definition that keeps them from blurring together.