From: Bob Briscoe <ietf@bobbriscoe.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] Fwd: my backlogged comments on the ECT(1) interim call
Date: Wed, 29 Apr 2020 14:37:02 +0100 [thread overview]
Message-ID: <537a840b-4c71-4ad2-8421-32c248eb69fa@bobbriscoe.net> (raw)
In-Reply-To: <00A6CD68-E37B-4505-BB96-476509937AFC@gmail.com>
Jonathan,
On 29/04/2020 10:49, Jonathan Morton wrote:
>> On 29 Apr, 2020, at 12:31 pm, Bob Briscoe<ietf@bobbriscoe.net> wrote:
>>
>>> Can the L4S and SCE folk run the rrul test some day soon? Please?
>> [BB] Does this measure the delay of every packet, so we can measure delay percentiles?
> As shown in our test results, Flent (which implements the RRUL test) is indeed now capable of tracking the latency experienced by individual TCP flows. It does not do so at the packet level, but at the socket level.
>
> Of course it is also possible to capture the traffic and analyse the traces offline, if you really do want packet-level detail.
1. So, why do you continue to use this approach? It hides all the larger
delays underneath a moving average. This seems more designed to hide
inconsistent delay results than to measure them. If a real-time
application waited only for the median delay before rendering, it would
have to discard the 50% of traffic in the upper median! TCP also
delivers nothing until the more delayed packets have been delivered to
get the stream in order. So median (or mean) delay is a meaningless metric.
2. I also notice you didn't address Dave's point about using short flows
as well as long. I don't believe I have ever seen a test from you or
PeteH with anything but long flows.
3. I should add that I know you personally have tried to address the
asymmetric capacity problem with the ACK thinning in CAKE.
Bob
> - Jonathan Morton
>
--
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/
next prev parent reply other threads:[~2020-04-29 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw5g8vMNEoV899tX=89HzHSG5s2E3sGU1EFVdqRkWryCqw@mail.gmail.com>
2020-04-27 19:26 ` Dave Taht
2020-04-29 9:31 ` Bob Briscoe
2020-04-29 9:46 ` [Ecn-sane] [tsvwg] " Sebastian Moeller
2020-04-29 10:32 ` Bob Briscoe
2020-04-29 11:21 ` Sebastian Moeller
2020-04-29 9:49 ` [Ecn-sane] " Jonathan Morton
2020-04-29 13:37 ` Bob Briscoe [this message]
2020-04-29 15:07 ` [Ecn-sane] [tsvwg] " Sebastian Moeller
2020-04-29 16:03 ` [Ecn-sane] " Jonathan Morton
2020-05-16 16:32 ` Dave Taht
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537a840b-4c71-4ad2-8421-32c248eb69fa@bobbriscoe.net \
--to=ietf@bobbriscoe.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=tsvwg@ietf.org \
/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