From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Sebastian Moeller <moeller0@gmx.de>, ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] results of two simple ECN tests
Date: Mon, 18 Feb 2019 11:24:18 -0800 [thread overview]
Message-ID: <CAA93jw4mQ5rOAwxQTZckWbv+cZ0xyC+u5nJ1wfiAzK1UG=SagQ@mail.gmail.com> (raw)
In-Reply-To: <C096F1D2-4F02-4604-B3FB-9F08CF53FBF5@heistp.net>
I appreciate the shot at going back to basics and the packet capture
driven tests.
ECN does help keep latency down at longer RTTs. But the bandwidth
improvements are rather minimal in this test case, and basically a
function of what would have been the drop rate. The pathological cases
I was discussing at one point (100 flows through a short low bandwidth
link) dramatically increase delay, cause starvation for other flows
(including new flows trying to start).
prev parent reply other threads:[~2019-02-18 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 11:26 Pete Heist
2019-02-17 13:02 ` Sebastian Moeller
2019-02-17 20:57 ` Pete Heist
2019-02-17 21:07 ` Sebastian Moeller
2019-02-18 10:33 ` Pete Heist
2019-02-18 19:24 ` Dave Taht [this message]
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='CAA93jw4mQ5rOAwxQTZckWbv+cZ0xyC+u5nJ1wfiAzK1UG=SagQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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