General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: tsvwg@ietf.org, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [tsvwg] how much of a problem is buffer bloat today?
Date: Thu, 21 Mar 2013 18:50:07 +0100	[thread overview]
Message-ID: <514B484F.2070902@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>

(cross posting to bloat)

On 03/13/2013 04:28 PM, Fred Baker (fred) wrote:
> On Mar 13, 2013, at 10:23 AM, Eliot Lear <lear@cisco.com> wrote:
> 
>> I don't have an answer to that question, but Mark Allman from ICIR did
>> attempt to characterize buffer bloat on the Internet through an
>> empirical study that appeared in the January edition of CCR.  You can
>> find a reference to that paper at the following URL:
>>
>> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041
>>
>> Eliot
> 
> Well, yes, he says that in his gigabit FTTH network he doesn't see megabit-scale problems.

Marks paper is /not/ about measuring buffer bloat in an FTTH network.
While he uses the FTTH network as /vantage point/, the paper actually
measures buffer bloat in various remote networks.

Marks paper is not the only study suggesting the extend of the problem
to be modest. The presented results are in line with recent findings by
Chirichella and Rossi [1]. Based on unpublished work, I can confirm the
low magnitude of the problem. I analyzed passive measurements of
residential users traffic from multiple continents (~60 million IPs
originating from 50\% of all ASes) and rarely find excessive RTTs that,
among other problems, can indicate the presence of buffer bloat.

In summary, bloated buffers exist and buffer bloat can be demonstrated,
but current findings suggest that it rarely occurs in practice. One
potential reason being that users do not often sustainably utilize
their uplink capacity and fill-up their potentially large queues.

Oliver

[1] To the Moon and back: are Internet bufferbloat delays really that large?
http://perso.telecom-paristech.fr/~drossi/paper/rossi13tma-a.pdf

       reply	other threads:[~2013-03-21 17:50 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 [this message]
2013-03-21 18:01     ` Jim Gettys
2013-03-21 18:14       ` Oliver Hohlfeld
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=514B484F.2070902@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