From: Noah Causin <n0manletter@gmail.com>
To: "Jonathan Morton" <chromatix99@gmail.com>, "Dave Täht" <dave@taht.net>
Cc: cake@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: Re: [Codel] [Cake] Proposing COBALT
Date: Fri, 3 Jun 2016 15:09:30 -0400 [thread overview]
Message-ID: <0eb223f9-2873-7f53-c2ce-c6867ddec17c@gmail.com> (raw)
In-Reply-To: <39F38477-A877-4C1B-9B7F-BB3358425F17@gmail.com>
Was the issue, where the drops and marks did not seem to occur, resolved?
On 5/26/2016 8:33 AM, Jonathan Morton wrote:
>> On 24 May, 2016, at 18:52, Dave Täht <dave@taht.net> wrote:
>>
>> My last attempts with cake the way it was had it performing miserably at
>> longer RTTs (try 50ms) vs codel or fq-codel - as in half the throughput
>> achieved by codel, at that RTT.
> There’s definitely something weird going on - as if the marks and drops reported by the stats are not actually occurring, except for the drops on queue overflow.
>
> Testing 50:1 flows on 1:10 bandwidth, for example, the single flow is stuck below the aggregate throughput of the 50, suggesting strongly that its acks are not being thinned. Cake used to be best-in-class on that very test.
>
> I will investigate further. But the solution may be to just perform the refactoring necessary to cleanly integrate COBALT, and eliminate subtle bugs by dint of simply sweeping away some unnecessarily gnarly code. I think COBALT’s API is probably a lot easier to integrate into a complex qdisc than Codel’s.
>
> - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2016-06-03 19:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:04 [Codel] " Jonathan Morton
2016-05-20 11:37 ` [Codel] [Cake] " moeller0
2016-05-20 12:18 ` Jonathan Morton
2016-05-20 13:22 ` moeller0
2016-05-20 14:36 ` Jonathan Morton
2016-05-20 16:03 ` David Lang
2016-05-20 17:31 ` Jonathan Morton
[not found] ` <CALnBQ5mNgHgFoTcvLxppv2P9XODc4D-4NObKyqbZJ0PccVkwiA@mail.gmail.com>
2016-05-20 16:43 ` Jonathan Morton
2016-05-23 18:30 ` Jonathan Morton
2016-05-24 13:47 ` Jeff Weeks
2016-05-24 14:07 ` Jonathan Morton
2016-05-24 15:52 ` Dave Täht
2016-05-24 15:56 ` Jonathan Morton
2016-05-24 16:02 ` Dave Taht
2016-05-26 12:33 ` Jonathan Morton
2016-06-03 19:09 ` Noah Causin [this message]
2016-06-03 19:34 ` Jonathan Morton
2016-06-04 1:01 ` Andrew McGregor
2016-06-04 6:23 ` Jonathan Morton
2016-06-04 13:55 ` Jonathan Morton
2016-06-04 14:01 ` moeller0
2016-06-04 14:16 ` Jonathan Morton
2016-06-04 15:03 ` moeller0
2016-06-04 17:10 ` Noah Causin
2016-06-04 17:49 ` Eric Dumazet
2016-06-04 19:55 ` Jonathan Morton
2016-06-04 20:56 ` Eric Dumazet
2016-06-27 3:56 ` Jonathan Morton
2016-06-27 7:59 ` moeller0
2016-05-20 13:41 ` David Lang
2016-05-20 13:46 ` moeller0
2016-05-20 14:04 ` David Lang
2016-05-20 14:42 ` Kathleen Nichols
2016-05-20 15:11 ` Jonathan Morton
2016-05-20 15:12 ` Jonathan Morton
2016-05-20 16:05 ` David Lang
2016-05-20 17:06 ` Jonathan Morton
2016-05-20 16:20 ` Rick Jones
2016-05-20 16:35 ` Jonathan Morton
2016-05-20 17:01 ` Rick Jones
2016-05-20 17:07 ` Jonathan Morton
2016-05-20 17:21 ` Rick Jones
2016-05-20 17:26 ` David Lang
2016-05-20 17:33 ` Jonathan Morton
2016-05-20 14:09 ` Jonathan Morton
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0eb223f9-2873-7f53-c2ce-c6867ddec17c@gmail.com \
--to=n0manletter@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave@taht.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