General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>,  bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [tsvwg] how much of a problem is buffer bloat today?
Date: Thu, 21 Mar 2013 19:14:03 +0100	[thread overview]
Message-ID: <514B4DEB.3020402@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>

> I believe you are actually measuring the *fraction of the time* your
> measurements show bad latency

Yes.

> The best data I've seen on how widespread the problem is is the ICSI
> Netalyzr scatter plots results

One has to be extremely careful on what to conclude from this data.
The Netalyzr data shows that bloated buffers _exist_, not that they
are _used_ in practice. Or as Mark has put it: "[it] shows that large
delays due to buffering can happen, not that they do happen."
Empirical evidence cited in my previous mail suggests that buffer
bloat does not happen often.

> I encourage everyone to run netalyzr and/or the mlabs tests for
> bufferbloat on your own broadband connections, or do simple copy and
> ping tests inside your own house over wifi to your local file servers....

While this will identify bloated buffers, it does not help in answering
what fraction of Internet users actually experience the problem.

Oliver

  reply	other threads:[~2013-03-21 18:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51408BF4.7090304@cisco.com>
     [not found] ` <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
2013-03-21 17:50   ` Oliver Hohlfeld
2013-03-21 18:01     ` Jim Gettys
2013-03-21 18:14       ` Oliver Hohlfeld [this message]
2013-03-21 18:28         ` Jim Gettys
2013-03-21 18:36           ` Dave Taht
2013-03-21 19:08 ` Oliver Hohlfeld
2013-03-21 19:25   ` Mikael Abrahamsson
2013-03-21 20:05     ` Jim Gettys
2013-03-22  4:27       ` Mikael Abrahamsson
2013-03-22  6:00         ` [Bloat] [aqm] " grenville armitage
2013-03-22 13:23           ` Mikael Abrahamsson
2013-03-22 13:31             ` Dave Taht
2013-03-26 17:25         ` Mirja Kuehlewind
2013-03-26 17:49           ` [Bloat] [tsvwg] [aqm] " Scheffenegger, Richard
2013-03-26 20:02             ` Hagen Paul Pfeifer
2013-03-21 20:04   ` [Bloat] [tsvwg] " David Lang
2013-03-21 20:47     ` Oliver Hohlfeld

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=514B4DEB.3020402@net.t-labs.tu-berlin.de \
    --to=oliver@net.t-labs.tu-berlin.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=tsvwg@ietf.org \
    /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