From: Sebastian Moeller <moeller0@gmx.de>
To: "Cake List" <cake@lists.bufferbloat.net>,
"Jonas Mårtensson" <martensson.jonas@gmail.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Cake] Cake not more CPU efficient than HTB+FQ-CoDel (anymore)?
Date: Wed, 11 Apr 2018 21:30:04 +0200 [thread overview]
Message-ID: <EFCDE2B1-1FE0-498F-8ACA-9CFA01762636@gmx.de> (raw)
In-Reply-To: <CF433B27-391D-401D-A6DE-A67E75574FD1@gmx.de>
Sorry,
just looked at the code and my recollection is wrong. I could have sworn that I purged cake as a shaper from simple.qos when I created piece_of_cake, but apparently that was just a fever dream...
Sorry for the noise.
> On Apr 11, 2018, at 21:26, Sebastian Moeller <moeller0@gmx.de> wrote:
>
>
>
> On April 11, 2018 8:55:12 PM GMT+02:00, "Jonas Mårtensson" <martensson.jonas@gmail.com> wrote:
>> On Wed, Apr 11, 2018 at 7:15 PM, Toke Høiland-Jørgensen <toke@toke.dk>
>> wrote:
>>
>>> Jonathan Morton <chromatix99@gmail.com> writes:
>>>
>>>>> 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%).
>>>
>>> It is definitely using Cake as the shaper; in besteffort mode, but
>> with
>>> nat and triple-isolation enabled I think. I'll run another test
>> tomorrow
>>> with those disabled.
>>
>>
>> Is there any difference between using simplest.qos and
>> piece_of_cake.qos
>> when Cake is used as qdisc?
>
> Yes, IIRC simplest.qos with cake as qdisc will use HTB as shaper and cake as leaf qdisc, while piece_of_cake.qos will use cake both as shaper and leaf qdisc. The former is only useful for comparative testing, for actual usage I recommend the later.
>
> Best Regards
> Sebastian
>
>
>>
>> /Jonas
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2018-04-11 19:30 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 [this message]
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=EFCDE2B1-1FE0-498F-8ACA-9CFA01762636@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=martensson.jonas@gmail.com \
--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