From: Kathleen Nichols <nichols@pollere.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat test measurements (was: Open Source Speed Test)
Date: Sat, 27 Aug 2016 08:19:12 -0700 [thread overview]
Message-ID: <448a25be-160f-701e-f56b-b3a33d49cff8@pollere.com> (raw)
In-Reply-To: <05056A85-894D-477F-A10D-C912C7D52C2F@gmail.com>
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
>
next prev parent reply other threads:[~2016-08-27 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 11:46 Rich Brown
2016-08-27 15:19 ` Kathleen Nichols [this message]
2016-08-27 16:03 ` [Bloat] Bufferbloat test measurements Alan Jenkins
2016-08-27 17:37 ` 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=448a25be-160f-701e-f56b-b3a33d49cff8@pollere.com \
--to=nichols@pollere.com \
--cc=bloat@lists.bufferbloat.net \
/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