From: Jonathan Morton <chromatix99@gmail.com>
To: david@lang.hm,cake@lists.bufferbloat.net
Subject: [Cake] Re: help request for cake on a large network
Date: Tue, 30 Sep 2025 03:55:28 +0000 [thread overview]
Message-ID: <dpxsc6.t3duwh.1hge2dj-qmf@smtp.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.2509280400350.14652@nftneq.ynat.uz>
On Sunday, 28 September 2025, David Lang wrote:
> I'm starting to prepare for the next Scale conference and we are switching from
> Juniper routers to Linux routers. This gives me the ability to implement cake.
>
> One problem we have is classes that tell everyone 'go download this' that
> trigger hundreds of people to hammer the network at the same time (this is both
> a wifi and a network bandwidth issue, wifi is being worked on)
>
> The network is pretty flat, a couple of subnets each on ipv4 and ipv6.
>
> Any suggestions on how to configure cake for this sort of environment where
> there are so many devices?
So far as Cake is concerned, the normal setup should work fine even under stress conditions. If there are too many simultaneous flows to achieve full flow isolation, it degrades gracefully to statistical multiplexing, and you still have the AQM working to keep everything responsive. Or rather, a thousand AQMs working in parallel...
Of course, this only matters when Cake is set up to be the bottleneck. If wifi is the bottleneck, you'll want a wifi stack with integrated fq_codel, which I believe still applies to only some hardware since it needs to manage the MAC queue which some devices don't expose. This has the extra smarts needed to adapt gracefully to wifi's foibles, and might already be enough to convert an effectively nonfunctional wifi into one that feels, if not fast, then at least reliable.
- Jonathan Morton
next prev parent reply other threads:[~2025-09-30 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 11:06 [Cake] " David Lang
2025-09-28 12:10 ` [Cake] " Sebastian Moeller
2025-09-28 12:17 ` David Lang
2025-09-28 12:12 ` Jaap de Vos
2025-09-28 12:38 ` David Lang
2025-09-28 12:56 ` Frantisek Borsik
2025-09-28 17:07 ` dave seddon
2025-09-28 17:26 ` David Lang
2025-09-30 5:18 ` Jonathan Morton
2025-09-30 3:55 ` Jonathan Morton [this message]
2025-09-30 4:30 ` dave seddon
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=dpxsc6.t3duwh.1hge2dj-qmf@smtp.gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
/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