From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id E102420016C for ; Tue, 8 Jan 2013 16:13:39 -0800 (PST) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id r090DcUO012099; Tue, 8 Jan 2013 16:13:38 -0800 Date: Tue, 8 Jan 2013 16:12:22 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Hal Murray In-Reply-To: <20130108190329.9E18980003B@ip-64-139-1-69.sjc.megapath.net> Message-ID: References: <20130108190329.9E18980003B@ip-64-139-1-69.sjc.megapath.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] bufferbloat paper X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2013 00:13:40 -0000 On Tue, 8 Jan 2013, Hal Murray wrote: >> Aside from their dataset having absolutely no reflection on the reality of >> the 99.999% of home users running at speeds two or three or *more* orders of >> magnitude below that speed, it seems like a nice paper. > > Did any of their 90 homes contained laptops connected over WiFi? Almost certinly, but if the connection from the laptop to the AP is 54M and the connection from the AP to the Internet is 1G, you are not going to have a lot of buffering taking place. You will have no buffering on the uplink side, and while you will have some buffering on the downlink side, 54M is your slowest connection and it takes a significantly large amount of data in flight to fill that for seconds. If your 54M wireless link is connected to a 768K DSL uplink (a much more typical connection), then it's very easy for the uplink side to generate many seconds worth of queueing delays, both from the high disparity in speeds and from the fact that the uplink is so slow. David Lang