General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Bufferbloat: Dark Buffers in the Internet
Date: Sat, 3 Dec 2011 02:08:25 -0700	[thread overview]
Message-ID: <CAK-n8j5pX4smpmEgMbzb7LOxCh+-bSks2bfc_1uWS15pGh=uQQ@mail.gmail.com> (raw)

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

                 reply	other threads:[~2011-12-03  9:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK-n8j5pX4smpmEgMbzb7LOxCh+-bSks2bfc_1uWS15pGh=uQQ@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox