From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Kathleen Nichols <nichols@pollere.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat test measurements
Date: Sat, 27 Aug 2016 17:03:22 +0100 [thread overview]
Message-ID: <63403b38-94fa-1670-908c-e14573f822a8@gmail.com> (raw)
In-Reply-To: <448a25be-160f-701e-f56b-b3a33d49cff8@pollere.com>
[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]
That's the simplest measure of bufferbloat though :).
Do you have a criticism in terms of dslreports.com? I think it's fairly
transparent, showing idle v.s. download v.s. upload. The headline
figures are an average, and you can look at all the data points. (You
can increase the measurement frequency if you're specifically interested
in that).
[random selection from Google]
http://www.dslreports.com/speedtest/419540
http://forum.kitz.co.uk/index.php?topic=15620.0
It's more aggressive than a single file download, but that's not
deliberately to exacerbate bufferbloat. It's just designed to measure
performance of prolonged downloads / streaming, in a competitively short
test. "For our busy lives", as the overused saying goes.
(The initial summary only gives a grade. The figure wouldn't be one of
the headlines their ISP advertises. Saying "100ms" would confuse
people. And the tests they're used to / compare with, show idle latency
instead.)
On 27/08/16 16:19, Kathleen Nichols wrote:
> 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
>>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Type: text/html, Size: 3219 bytes --]
next prev parent reply other threads:[~2016-08-27 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 11:46 [Bloat] Bufferbloat test measurements (was: Open Source Speed Test) Rich Brown
2016-08-27 15:19 ` Kathleen Nichols
2016-08-27 16:03 ` Alan Jenkins [this message]
2016-08-27 17:37 ` [Bloat] Bufferbloat test measurements Kathleen Nichols
2016-08-27 19:18 ` Alan Jenkins
2016-08-27 19:39 ` Alan Jenkins
2016-08-27 23:39 ` jb
2016-08-28 0:14 ` Kathleen Nichols
2016-08-28 2:23 ` jb
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=63403b38-94fa-1670-908c-e14573f822a8@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=nichols@pollere.com \
/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