From: Jonathan Morton <chromatix99@gmail.com>
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:41:06 +0300 [thread overview]
Message-ID: <CE52664C-7F35-4299-A0E1-531F42A2B04A@gmail.com> (raw)
In-Reply-To: <87in8xahqp.fsf@toke.dk>
> On 11 Apr, 2018, at 6:24 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> So, um, did we cram so many features into Cake that it no longer uses
> less CPU? Can anyone confirm these results?
To be sure about this, it seems wise to configure Cake to turn off as many of the new features as possible. That means selecting "besteffort flows nonat" mode at least.
I forget whether simplest.qos correctly uses the built-in shaper with Cake, rather than just layering it with HTB as usual. If not, then of course Cake will use more CPU, and we should be grateful that it's by a relatively small margin (maybe 15%).
There's also a minor complication in that Cake and fq_codel behave differently when handed superpackets. A fair comparison requires switching aggregation modes off for both of them.
All of my working hardware tends to saturate either the link or a PCI bus before hitting a CPU limit, so I can't reproduce it locally.
- Jonathan Morton
next prev parent reply other threads:[~2018-04-11 15:41 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 [this message]
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
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=CE52664C-7F35-4299-A0E1-531F42A2B04A@gmail.com \
--to=chromatix99@gmail.com \
--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