Re: [Bloat] Bufferbloat: Dark Buffers in the Internet (ACT II, Scene I)

Re: [Bloat] Bufferbloat: Dark Buffers in the Internet (ACT II, Scene I)

[Dave Taht]

Aggh! It's out already?

re:

http://queue.acm.org/detail.cfm?id=2071893

All: This collaboration between Kathie Nichols and JG is a major
update, enhancement, revision and replacement of the original 'Dark
Buffers' presentations,  and contains quite a few new bits of data,
several corrections for accuracy, new analogies, some new, clearer
plots via Van Jacobson, and a whole lot more.

And my own moment of major enlightenment came from... ya know... I'm
not gonna tell ya. It's a good piece, well worth reading,
even if you think you already understand everything there is to
understand about bufferbloat.

(hint - see figure 4B and the surrounding paragraphs). Suddenly a
whole lot of very fuzzy data made a whole lot of sense to,me.

Please pass it along.


On Sat, Dec 3, 2011 at 10:08 AM, Jim Reisert AD1C
<jjreisert@alum.mit.edu> wrote:
> Networks without effective AQM may again be vulnerable to congestion collapse.
>
>
> Jim Gettys, Bell Labs, Alcatel-Lucent; and Kathleen Nichols, Pollere Inc.
>
>
> Today's networks are suffering from unnecessary latency and poor
> system performance. The culprit is bufferbloat, the existence of
> excessively large and frequently full buffers inside the network.
> Large buffers have been inserted all over the Internet without
> sufficient thought or testing. They damage or defeat the fundamental
> congestion-avoidance algorithms of the Internet's most common
> transport protocol. Long delays from bufferbloat are frequently
> attributed incorrectly to network congestion, and this
> misinterpretation of the problem leads to the wrong solutions being
> proposed.
>
> Congestion is an old problem on the Internet, appearing in various
> forms with different symptoms and causing major problems. Buffers are
> essential to the proper functioning of packet networks, but overly
> large, unmanaged, and uncoordinated buffers create excessive delays
> that frustrate and baffle end users. Many of the issues that create
> delay are not new, but their collective impact has not been widely
> understood. Thus, buffering problems have been accumulating for more
> than a decade. We strive to present these problems with their impacts
> so that the community can understand and act upon the problem and, we
> hope, learn to prevent future problems.
>
> This article does not claim to be the first to identify the problems
> of excessive buffering, but is instead intended to create a wider
> understanding of the pervasive problem and to give a call to action.
>
>
> http://queue.acm.org/detail.cfm?id=2071893
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net