From: Jonathan Morton <chromatix99@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] debloats/day metric?
Date: Mon, 27 Aug 2018 11:02:02 +0300 [thread overview]
Message-ID: <0C7983D3-4452-4DEF-87A6-2200A106FAB9@gmail.com> (raw)
In-Reply-To: <760F79E7-EA45-46B9-AA0F-7300D0242E44@heistp.net>
> On 27 Aug, 2018, at 10:44 am, Pete Heist <pete@heistp.net> wrote:
>
> …request pairs, one given strict priority at the bottleneck and one best effort, then measure the difference between the two (for both RTT and OWD).
>
> Assuming this yields useful data…
For the overwhelming majority of bloated bottlenecks, it will not - because they have zero concept of "strict priority".
- Jonathan Morton
next prev parent reply other threads:[~2018-08-27 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 16:57 Dave Taht
2018-08-27 7:44 ` Pete Heist
2018-08-27 8:02 ` Jonathan Morton [this message]
2018-08-27 9:32 ` Pete Heist
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=0C7983D3-4452-4DEF-87A6-2200A106FAB9@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=pete@heistp.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