When Buffers Backfire

Written by Studio AM.

Internet traffic often arrives in bursts. Routers use buffers to hold packets briefly when arrivals exceed the next link's capacity. A modest queue can absorb a short surge, allowing traffic to pass without immediately discarding every excess packet.

But a large buffer can remain full under sustained load. Each arriving packet then waits behind a long queue. A connection with high data capacity may still feel unresponsive: a video call can lag while a file uploads. This excessive queueing delay is called bufferbloat.

Feedback helps explain the problem. Many transport protocols reduce their sending rate when packet loss indicates congestion. A large queue can postpone that signal by accepting more traffic before it drops packets. The sender continues at a rate that keeps the queue busy, and interactive traffic waits along with the bulk transfer.

Active queue management addresses this by dropping packets or marking congestion before the queue becomes persistently long. The aim is to keep enough buffering for bursts while providing timely feedback during overload.

The lesson extends beyond networks: storage can cushion short fluctuations, but a system also needs a way to recognize sustained pressure and respond. More capacity to hold a problem is not the same as faster recovery from it.

Questions

Choose an answer. The explanation appears after you answer.

  1. Question 1 of 4

    Which statement best captures the passage's central point?

  2. Question 2 of 4

    Why can a large queue delay a sender's reduction in its sending rate?

  3. Question 3 of 4

    What does “absorb” mean in the first paragraph?

  4. Question 4 of 4

    What does active queue management do before a queue becomes persistently long?

Score: none answered yet.

More passages

Practise reading