Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <pete@eventide.io>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake not more CPU efficient than HTB+FQ-CoDel (anymore)?
Date: Wed, 11 Apr 2018 18:03:43 +0200	[thread overview]
Message-ID: <DFE97D2B-AFFB-44B7-A6DD-BD7B8A2EC36C@eventide.io> (raw)
In-Reply-To: <87in8xahqp.fsf@toke.dk>

For what it’s worth, that’s what I also saw testing Cake on the APU2 late last year, and the ER-X platform earlier. I actually never knew that Cake used less CPU at some point. Sorry for no supporting detail... :)

Pete

> On Apr 11, 2018, at 5:24 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> So we've been saying that one of the benefits of Cake is less CPU usage;
> but while trying to benchmark this I got results that would seem to
> indicate the opposite.
> 
> See attached graph + data files. Basically, I setup a shaper on an
> Archer C7 with sqm-scripts simplest.qos. Both HTB+FQ-CoDel and Cake
> manages to shape at 250 Mbps, where Cake even shows a bit lower latency.
> That is good.
> 
> However, when I change the configuration to 400 Mbps (more than the
> Archer CPU can handle), Cake tops out at ~260 Mbps, while HTB+FQ-CoDel
> manages ~305 Mbps and a slightly lower latency. In both cases I see the
> characteristic 95% sirq CPU usage in 'top' on the Archer while the test
> is running.
> 
> So, um, did we cram so many features into Cake that it no longer uses
> less CPU? Can anyone confirm these results?
> 
> The tests were run on an openwrt nightly image from today, which has the
> latest Cake version from the Cobalt branch.
> 
> 
> -Toke
> 
> <cake-vs-fqcodel-cpulimit.pdf><tcp_1up-2018-04-11T165952.024206.FQ-CoDel_250_Mbps.flent.gz><tcp_1up-2018-04-11T170134.227613.Cake_250_Mbps.flent.gz><tcp_1up-2018-04-11T170457.254899.Cake_400_Mbps.flent.gz><tcp_1up-2018-04-11T170647.320916.FQ-CoDel_400_Mbps.flent.gz>_______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  parent reply	other threads:[~2018-04-11 16:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 15:24 Toke Høiland-Jørgensen
2018-04-11 15:41 ` Jonathan Morton
2018-04-11 17:15   ` Toke Høiland-Jørgensen
2018-04-11 17:23     ` Jonathan Morton
2018-04-11 17:47       ` Toke Høiland-Jørgensen
2018-04-11 17:59         ` Jonathan Morton
2018-04-11 18:55     ` Jonas Mårtensson
2018-04-11 19:08       ` Toke Høiland-Jørgensen
2018-04-11 19:26       ` Sebastian Moeller
2018-04-11 19:30         ` Sebastian Moeller
2018-04-11 19:56           ` Jonas Mårtensson
2018-04-12 10:48     ` Toke Høiland-Jørgensen
2018-04-11 16:03 ` Pete Heist [this message]
2018-04-11 17:16   ` Toke Høiland-Jørgensen
2018-04-14  4:48 ` There is cake qdisc manual Y

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DFE97D2B-AFFB-44B7-A6DD-BD7B8A2EC36C@eventide.io \
    --to=pete@eventide.io \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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