[Bloat] First draft of complete "Bufferbloat And You" enclosed.

[Sean Conner]

It was thus said that the Great Eric Raymond once stated:
> Justin McCann <jneilm at gmail.com>:
> > This may be intentional, but the text launches into an explanation of
> > why bufferbloat is bad without concisely explaining what it is--- you
> > have to read the whole first two sections before it's very clear.
> 
> Not intentional, exactly, but's inherent.  Thec reader *can't* get what
> bufferbloat.
> 
> > The second of the three main tactics states, "Second, we can decrease
> > buffer sizes.  This cuts the delay due to latency and decreases the
> > clumping effect on the traffic." Latency *is* delay; perhaps "cuts the
> > delay due to buffering" or "due to queueing" would be better, if more
> > tech-ese.
> 
> Good catch, I'll fix.
>  
> > I've re-read through the Bell Labs talk, and some of the earlier
> > posts, but could someone explain the "clumping" effect? I understand
> > the wild variations in congestion windows ("swing[ing] rapidly and
> > crazily between emptiness and overload"), but clumping makes me think
> > of closely spaced packet intervals.
> 
> It's intended to.  This is what I got from jg's talk, and I wrote the
> SOQU scenario to illustrate it. If my understanding is incorrect (and
> I see that you are saying it is) one of the real networking people
> here needs to whack me with the enlightenment stick.
> 
> The underlying image in my just-so stories about roads and parking lots
> is that packet flow coming in smooth on the upstream side of a buffwer
> gets turned into a buffer fill, followed by a burst of packets as it 
> overflows, followed by more data coming into the buffer, followed by
> overflow...repeat.

  I didn't care for that analogy, roads and parking lots.  Better might be
freeways and interchanges, because the buffers are where traffic moves from
one freeway (the path between router A and B) to another (the path between
router B and C).  If the interchange is small (say, a lane that's only a few
hundred yards long) then any delay becomes immediately apparent.  Buffer
bloat is analogous to either increasing the number of lanes in the
interchange, or making the interchange longer (here in South Florida, the
interchange between I-595 W and I-95 N is two lanes two miles long---I am
not making this up).

  The analogy also reminded me of traffic physics
(http://amasci.com/amateur/traffic/traffic1.html).  I'm not sure if that has
any bearing and is one reason why I tend to dislike analogies of computer
topics to real world phenomenon---there are so many problems and exceptions
that it tends to cloud the issue.

  I took buffer bloat to be that the inflow of packets exceeds the outflow
of packets, and that the buffer does exactly that---buffers the excess,
which delays the dropping of packets that lead to congestion control to kick
in.

  -spc