From: Kathleen Nichols <nichols@pollere.com>
To: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat test measurements
Date: Sat, 27 Aug 2016 17:14:13 -0700 [thread overview]
Message-ID: <5c615f4b-6162-915d-897c-871c3e843ed2@pollere.com> (raw)
In-Reply-To: <CAH3Ss94EbydWtBxnmjMmXwT=4LAdy5F64RQ+mHekcV3K9BvHNg@mail.gmail.com>
Hi, Justin,
Thanks for the explanations. So the grade is for the user not the ISP?
I just have to point out that the below jumped out at me a bit. A user
can fully use the link bandwidth capacity and not have an unacceptable
latency. After all, that's the goal of AQM. But, yes, there are those
pesky lurking buffers in the path which the user might unhappily
use to their full capacity and then latency can be unacceptable.
Kathie
On 8/27/16 4:39 PM, jb wrote:
>
> Generally if a user does not use their connection to full capacity, latency
> is acceptable (but obviously the buffers are still there, lurking).
> Bursts and
> so on can discover them again but the effects are transient.
next prev parent reply other threads:[~2016-08-28 0:14 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 ` [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 [this message]
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=5c615f4b-6162-915d-897c-871c3e843ed2@pollere.com \
--to=nichols@pollere.com \
--cc=bloat@lists.bufferbloat.net \
--cc=justin@dslr.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