From: Kathleen Nichols <nichols@pollere.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Open Source Speed Test (was fast.com - Netflix's speed monitoring)
Date: Fri, 26 Aug 2016 16:13:21 -0700 [thread overview]
Message-ID: <90667e99-1334-af36-5879-3b4ed362ed68@pollere.com> (raw)
In-Reply-To: <1C99BD90-7688-4168-814D-57DA12F0F08C@cable.comcast.com>
I think it might be useful to say these tests measure the maximum
*potential* for
bufferbloat. That is, they plumb the depths of the buffers in the path.
I tried running
dslreports while I was running a video and though dslreports ramps
delays up to 700ms,
before and after that peak delay is more like 45ms. I don't think large
buffers are going
to go away, what matters is whether they are getting filled up.
So, is "bufferbloat" the existence of large buffers or the existence of
large queues? I think
the latter.
Kathie
On 8/24/16 10:28 AM, Livingood, Jason wrote:
>> Why doesn't the test measure bufferbloat like FLENT or dslreports test?
>
> We have not gotten to it yet; it is in our backlog. We’re hoping folks might help prior to the hackathon or at the hackathon… ☺
>
> Jason
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
next prev parent reply other threads:[~2016-08-26 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:42 Livingood, Jason
2016-08-24 16:08 ` Stephen Hemminger
2016-08-24 17:28 ` Livingood, Jason
2016-08-26 23:13 ` Kathleen Nichols [this message]
2016-08-26 23:20 ` David Lang
2016-08-26 23:37 ` Kathleen Nichols
2016-08-27 1:06 ` David Lang
2016-08-27 5:02 ` grenville armitage
2016-08-27 12:16 ` Jonathan Morton
2016-08-27 0:20 ` Benjamin Cronce
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=90667e99-1334-af36-5879-3b4ed362ed68@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