From: Dave Taht <dave.taht@gmail.com>
To: Hari Balakrishnan <hari@csail.mit.edu>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] copa congestion control
Date: Mon, 18 Jun 2018 12:56:55 -0700 [thread overview]
Message-ID: <CAA93jw6seYpNq0gkfuzcHKZH_u6AXWJopf28NkKmE4CQdg+Tfw@mail.gmail.com> (raw)
In-Reply-To: <686ECD4B-0F21-408E-B129-42E87724EA0C@csail.mit.edu>
On Mon, Jun 18, 2018 at 12:45 PM, <hari@csail.mit.edu> wrote:
> Thanks, Dave, for the comments. The paper does have results comparing to Cubic-over-sfqCodel in a couple of sections. For example, "In an experiment to test RTT-fairness, Copa, Cubic, Cubic over CoDel and Newreno obtained Jain fairness indices of 0.76, 0.12, 0.57 and 0.37 respectively (higher the better).” Figure 6 in the paper illustrates.
It is not clear from the paper it was actually sfqcodel under test at
any point. The codel results look like codel results.
My largely empirical analysis is that delay based tcp's work great
against fq_codel derived aqms, even competing against cubic or bbr. In
the case of copa
I would expect the loss based portion of the algo to rarely engage,
and the relative smoothness-es of copa for rate changes to work quite
well against the smoother rate sharing flow-queuing generally
achieves.
Not clear if you were using tcp pacing, either.
Got patches? Test scripts?
>
> Most of the other results were obtained over real-world paths, or via trace-driven emulation where the traces were obtained over real paths. In those cases we are not sure how to compare with AQM.
Well, I would certainly love it if one day y'all tore apart
https://www.usenix.org/system/files/conference/atc17/atc17-hoiland-jorgensen.pdf
and https://arxiv.org/abs/1804.07617
against whatever you are dreaming up. :)
>
> Hari
>
>> On Jun 18, 2018, at 3:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> Looks promising, like all papers do...
>>
>> https://www.usenix.org/system/files/conference/nsdi18/nsdi18-arun.pdf
>>
>> Keep hoping folk will try their CC-scheme de-jure against one of the existing
>> aqm designs....
>>
>> --
>>
>> Dave Täht
>> CEO, TekLibre, LLC
>> http://www.teklibre.com
>> Tel: 1-669-226-2619
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
prev parent reply other threads:[~2018-06-18 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 19:09 Dave Taht
[not found] ` <686ECD4B-0F21-408E-B129-42E87724EA0C@csail.mit.edu>
2018-06-18 19:56 ` 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/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=CAA93jw6seYpNq0gkfuzcHKZH_u6AXWJopf28NkKmE4CQdg+Tfw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hari@csail.mit.edu \
/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