From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from homiemail-a55.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C02B43B25E for ; Sat, 27 Aug 2016 11:19:13 -0400 (EDT) Received: from homiemail-a55.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a55.g.dreamhost.com (Postfix) with ESMTP id D72F21612; Sat, 27 Aug 2016 08:19:12 -0700 (PDT) Received: from kmnimac.local (unknown [50.136.231.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nichols@pollere.net) by homiemail-a55.g.dreamhost.com (Postfix) with ESMTPSA id B49CB1608; Sat, 27 Aug 2016 08:19:12 -0700 (PDT) To: bloat@lists.bufferbloat.net References: <05056A85-894D-477F-A10D-C912C7D52C2F@gmail.com> From: Kathleen Nichols Message-ID: <448a25be-160f-701e-f56b-b3a33d49cff8@pollere.com> Date: Sat, 27 Aug 2016 08:19:12 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <05056A85-894D-477F-A10D-C912C7D52C2F@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] Bufferbloat test measurements (was: Open Source Speed Test) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2016 15:19:13 -0000 Yeah. I admit to muddying the waters because I think of the size of a buffer as being in megabytes and the size of a queue (latency) as being in milliseconds. I think the tests attempt to measure the worst possible latency/queue that can occur on a path. On 8/27/16 4:46 AM, Rich Brown wrote: > It has always been my intent to define bufferbloat as *latency*. The > first sentence on www.bufferbloat.net says, "Bufferbloat is the > undesirable latency that comes from a router or other network > equipment buffering too much data." > > That definition focuses on observable/measurable values. It sidesteps > objections I've seen on the forums, "How could $TEST measure the size > of buffers?" > > So what matters is whether the buffers (of any size) are filling up. > _______________________________________________ Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >