Bandwidth vs Throughput: What is the Difference?
Understand bandwidth vs throughput, why real speed is lower than advertised capacity, and how goodput fits in — interview Q&A.
Expected Interview Answer
Bandwidth is the theoretical maximum data rate a link can carry, usually stated in bits per second, while throughput is the actual data rate achieved in practice, which is always less than or equal to bandwidth due to overhead, congestion, latency, and packet loss.
Bandwidth describes the capacity of a channel — a "1 Gbps" link means it is rated to carry up to one gigabit per second under ideal conditions, similar to the width of a pipe. Throughput is what actually flows through that pipe once real-world factors are accounted for: protocol overhead (headers, acknowledgements), the TCP congestion window still ramping up, competing traffic sharing the link, retransmissions from packet loss, and the round-trip time limiting how much data can be “in flight” at once. A link with high bandwidth but high latency or heavy congestion can deliver disappointing throughput, which is why engineers measure actual throughput with tools rather than assuming it equals the advertised bandwidth. Goodput is a related, even stricter term — the throughput of only useful application data, excluding retransmitted or protocol-overhead bytes.
- Bandwidth sets the theoretical ceiling for a link’s capacity
- Throughput reflects real-world achieved performance
- Understanding the gap helps diagnose network performance issues
- Goodput further isolates useful data from retransmissions and overhead
AI Mentor Explanation
Bandwidth is like the maximum width of a boundary rope marking how large the field theoretically is for hitting sixes, while throughput is how many runs a batter actually scores in an over given bowling variations, fielding placement, and weather. A field can be enormous in theory, but a tight bowling attack and good fielders reduce the runs actually scored below the field’s theoretical potential. The gap between the field’s size and the runs on the board is exactly the gap between bandwidth and throughput.
Step-by-Step Explanation
Step 1
Rated capacity
Bandwidth is the advertised or provisioned maximum data rate of a link (e.g., 1 Gbps).
Step 2
Real-world factors
Protocol overhead, latency, congestion, and packet loss reduce what is actually achievable.
Step 3
Measured throughput
Throughput is the actual data rate observed in practice, always ≤ bandwidth.
Step 4
Goodput
A stricter measure counting only useful application data, excluding retransmissions and overhead.
What Interviewer Expects
- Clear definition distinguishing theoretical capacity from actual achieved rate
- Understanding of factors that reduce throughput below bandwidth
- Awareness that latency and TCP window size affect achievable throughput
- Knowledge of tools used to measure real throughput
Common Mistakes
- Using bandwidth and throughput interchangeably
- Assuming a link always performs at its advertised bandwidth
- Forgetting that high latency can cap throughput even with high bandwidth
- Not distinguishing throughput from goodput (useful data only)
Best Answer (HR Friendly)
“Bandwidth is the advertised maximum speed of a connection, like the width of a pipe. Throughput is how much water actually flows through it once you account for real-world friction — network congestion, overhead, and delays. A connection might be sold as 1 Gbps, but the actual speed you experience day to day is throughput, and it is almost always a bit lower than the advertised bandwidth.”
Code Example
# Test achieved throughput between two hosts using iperf3
iperf3 -c 203.0.113.1 -t 10
# [ ID] Interval Transfer Bitrate
# [ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec (link rated at 1000 Mbps)
# Check interface link speed (the advertised bandwidth)
ethtool eth0 | grep SpeedFollow-up Questions
- How does the TCP congestion window affect achievable throughput?
- What is the bandwidth-delay product and why does it matter?
- How does packet loss reduce effective throughput on a high-latency link?
- What is the difference between throughput and goodput?
MCQ Practice
1. What does bandwidth represent?
Bandwidth is the theoretical maximum data rate a link is rated or provisioned to carry.
2. Why is throughput usually lower than bandwidth?
Protocol overhead, congestion, latency, and packet loss all reduce actual throughput below rated bandwidth.
3. What does “goodput” specifically measure?
Goodput is a stricter measure than throughput, counting only useful application-level data.
Flash Cards
What is bandwidth? — The theoretical maximum data rate a link can carry, e.g. 1 Gbps.
What is throughput? — The actual data rate achieved in practice, always ≤ bandwidth.
What factors reduce throughput below bandwidth? — Protocol overhead, congestion, latency, and packet loss/retransmissions.
What is goodput? — Throughput counting only useful application data, excluding overhead and retransmissions.