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 <moell...@gmx.de> wrote:
> On April 11, 2018 8:55:12 PM GMT+02:00, "Jonas Mårtensson"
> <martensson.jo...@gmail.com> wrote:
>> On Wed, Apr 11, 2018 at 7:15 PM, Toke Høiland-Jørgensen <t...@toke.dk>
>>> Jonathan Morton <chromati...@gmail.com> writes:
>>>>> On 11 Apr, 2018, at 6:24 pm, Toke Høiland-Jørgensen <t...@toke.dk>
>>>>> So, um, did we cram so many features into Cake that it no longer
>>>>> less CPU? Can anyone confirm these results?
>>>> To be sure about this, it seems wise to configure Cake to turn off
>>>> many of the new features as possible. That means selecting
>>>> flows nonat" mode at least.
>>>> I forget whether simplest.qos correctly uses the built-in shaper
>>>> Cake, rather than just layering it with HTB as usual. If not, then
>>>> course Cake will use more CPU, and we should be grateful that it's
>>>> a relatively small margin (maybe 15%).
>>> It is definitely using Cake as the shaper; in besteffort mode, but
>>> nat and triple-isolation enabled I think. I'll run another test
>>> with those disabled.
>> Is there any difference between using simplest.qos and
>> 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
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> Cake mailing list
Cake mailing list