General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Foulkes <jf@jonathanfoulkes.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] CAKE in openwrt high CPU
Date: Tue, 1 Sep 2020 18:18:02 +0200	[thread overview]
Message-ID: <4E67F6C6-5187-4052-B7CA-177245F01CC0@gmx.de> (raw)
In-Reply-To: <5DBFB383-13E8-4587-BE49-1767471D7D59@jonathanfoulkes.com>

HI Jonathan,

> On Sep 1, 2020, at 17:41, Jonathan Foulkes <jf@jonathanfoulkes.com> wrote:
> 
> Toke, that link returns a 404 for me.
> 
> For others, I’ve found that testing cake throughput with isolation options enabled is tricky if there are many competing connections. 

	Are you talking about the fact that with competing connections, you only see the current isolation quantum's equivalent f the actual rate? In that case maybe parse the "tc -s qdisc" output to get an idea how much data/packets cake managed to push through in total in each direction instead of relaying on the measured goodput? I am probably barking up the wrong tree here...

> Like I keep having to tell my customers, fairness algorithms mean no one device will ever gain 100% of the bandwidth so long as there are other open & active connections from other devices.

	That sounds like solid advice ;) Especially in the light of the exceedingly useful "ingress" keyword, which under-load-will drop depending on a flow's "unresponsiveness" such that more responsive flows end up getting a somewhat bigger share of the post-cake throughput...

> 
> That said, I’d love to find options to increase throughput for single-tin configs.

	With or without isolation options?

Best Regards
	Sebastian

> 
> Cheers,
> 
> Jonathan
> 
>> On Aug 31, 2020, at 7:35 AM, Toke Høiland-Jørgensen via Bloat <bloat@lists.bufferbloat.net> wrote:
>> 
>> Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net> writes:
>> 
>>> Hi,
>>> 
>>> I migrated to an APU2 (https://www.pcengines.ch/apu2.htm) as residential 
>>> router, from my previous WRT1200AC (marvell armada 385).
>>> 
>>> I was running OpenWrt 18.06 on that one, now I am running latest 19.07.3 
>>> on the APU2.
>>> 
>>> Before I had 500/100 and I had to use FQ_CODEL because CAKE took too much 
>>> CPU to be able to do 500/100 on the WRT1200AC. Now I upgraded to 1000/1000 
>>> and tried it again, and even the APU2 can only do CAKE up to ~300 
>>> megabit/s. With FQ_CODEL I get full speed (configure 900/900 in SQM in 
>>> OpenWrt).
>>> 
>>> Looking in top, I see sirq% sitting at 50% pegged. This is typical what I 
>>> see when CPU based forwarding is maxed out. From my recollection of 
>>> running CAKE on earlier versions of openwrt (17.x) I don't remember CAKE 
>>> using more CPU than FQ_CODEL.
>>> 
>>> Anyone know what's up? I'm fine running FQ_CODEL, it solves any 
>>> bufferbloat but... I thought CAKE supposedly should use less CPU, not 
>>> more?
>> 
>> Hmm, you say CAKE and FQ-Codel - so you're not enabling the shaper (that
>> would be FQ-CoDel+HTB)? An exact config might be useful (or just the
>> output of tc -s qdisc).
>> 
>> If you are indeed not shaping, maybe you're hitting the issue fixed by this commit?
>> 
>> https://github.com/dtaht/sch_cake/commit/3152477235c934022049fcddc063c45d37ec10e6n
>> 
>> -Toke
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  parent reply	other threads:[~2020-09-01 16:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 17:27 Mikael Abrahamsson
2020-08-30 17:52 ` Dave Taht
2020-08-31 11:35 ` Toke Høiland-Jørgensen
2020-08-31 12:22   ` Mikael Abrahamsson
2020-08-31 13:29     ` Toke Høiland-Jørgensen
2020-09-03 13:10       ` Mikael Abrahamsson
2020-09-03 13:29         ` Toke Høiland-Jørgensen
2020-09-03 13:34           ` Sebastian Moeller
2020-09-03 13:32         ` Sebastian Moeller
2020-09-04 13:37           ` Mikael Abrahamsson
2020-09-04 14:12             ` Sebastian Moeller
2020-09-01 15:41   ` Jonathan Foulkes
2020-09-01 16:11     ` Toke Høiland-Jørgensen
2020-09-01 16:25       ` Sebastian Moeller
2020-09-01 18:45         ` Toke Høiland-Jørgensen
2020-09-01 19:05           ` Jonathan Morton
2020-09-01 21:09             ` Toke Høiland-Jørgensen
2020-09-01 19:01       ` Jonathan Foulkes
2020-09-01 21:11         ` Toke Høiland-Jørgensen
2020-09-02 20:26           ` Jonathan Foulkes
2020-09-02 20:57             ` Toke Høiland-Jørgensen
2020-09-03 13:19           ` Mikael Abrahamsson
2020-09-03 13:27             ` Luca Muscariello
2020-09-03 14:32               ` Toke Høiland-Jørgensen
2020-09-03 15:31                 ` Luca Muscariello
2020-09-03 18:39                   ` Toke Høiland-Jørgensen
2020-09-03 18:53                 ` Jonathan Morton
2020-09-03 22:14                 ` [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU) David Collier-Brown
2020-09-04  1:19                   ` Jonathan Morton
2020-09-04 13:41                     ` Mikael Abrahamsson
2020-09-04 11:11                   ` Toke Høiland-Jørgensen
2020-09-03 13:27             ` [Bloat] CAKE in openwrt high CPU Toke Høiland-Jørgensen
2020-09-01 16:18     ` Sebastian Moeller [this message]
2020-09-01 19:31       ` Jonathan Foulkes
2020-09-01 20:04         ` Sebastian Moeller
2020-09-01 20: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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=4E67F6C6-5187-4052-B7CA-177245F01CC0@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jf@jonathanfoulkes.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