Technology · Level 4 · 203 words
When Buffers Backfire
Original passage © Studio AM, written for Fluency.
Internet traffic moves in bursts, so every router keeps a buffer: a queue where packets wait when they arrive faster than the link ahead can carry. A modest buffer is useful; it absorbs a burst that would otherwise be thrown away. Engineers reasoned that if some buffer was good, more was safer, and when memory became cheap, buffers grew enormous.
Then fast connections began to feel slow. A video call stutters while a file uploads. Engineers named the sickness bufferbloat. Once a giant buffer fills, each packet waits behind everything ahead; the waiting, not the moving, is the delay.
The deeper fault is a silenced signal. A sender slows down when the network drops its packets: a drop is bad news, but it is also the message that the road is full. A deep buffer delays that message: it stores excess traffic instead of dropping it, so the sender keeps pushing into an ever-longer line. A queue smooths traffic, but it also carries feedback; too deep, and feedback arrives too late to matter.
Modern routers keep their queues deliberately short. The lesson travels beyond networks: in a system steered by feedback, quietly absorbing a problem does not solve it. It postpones the news.
Source: Written for Fluency. Original passage © Studio AM, written for Fluency.