From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <oliver@net.t-labs.tu-berlin.de>
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de
	[IPv6:2001:470:96b9:4:130:149:220:252])
	by huchra.bufferbloat.net (Postfix) with ESMTP id 16DA721F1D2
	for <bloat@lists.bufferbloat.net>; Thu, 21 Mar 2013 11:14:05 -0700 (PDT)
Received: from [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838]
	(ibis.net.t-labs.tu-berlin.de
	[IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838])
	by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 1ED9B4C4C25; 
	Thu, 21 Mar 2013 19:14:04 +0100 (CET)
Message-ID: <514B4DEB.3020402@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 19:14:03 +0100
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, 
 bloat <bloat@lists.bufferbloat.net>
References: <51408BF4.7090304@cisco.com>
	<8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
	<514B484F.2070902@net.t-labs.tu-berlin.de>
	<CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>
In-Reply-To: <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Bloat] [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:14:05 -0000

> 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