From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: [Cake] Re: help request for cake on a large network
Date: Sun, 28 Sep 2025 05:17:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.2509280513450.14652@nftneq.ynat.uz> (raw)
In-Reply-To: <06DAA0CB-70EF-4FDD-BD3D-16A4FC28AD12@gmx.de>
Sebastian Moeller wrote:
> Hi David,
>
> while I have no real answer for your questions (due to never having had that kind of load in my home network ;) ) I would like to ask you to make take scripted captures of tc -s qdisc for the wan interface is reasonable short intervals (say every 10 minutes?) as that might be just what we need to actually answer your question.
I will do that, however the network is only up under load for 4 days a year, so
it's a slow feedback loop :-)
I would welcome any other suggestions for data to gather.
>> On 28. Sep 2025, at 13:06, David Lang <david@lang.hm> 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)
>
> So one issue might be that with several 100 users the default compile-time
> size of queues (1024, IIRC) that cake will entertain might be too little, even
> in light of the 8 way assoziative hashing design. I believe this can be
> changed (within limits) only by modifying at source and recompilation of the
> kernel, if that should be needed at all.
custom compiling a kernel is very much an option (and this sort of tweaking is
the sort of thing I'm expecting to need to do)
The conference is in March, so we have some time to think about this and
customize things, just no chance to test before the show.
> I wonder whether multi-queue cake would not solve this to some degree, as I
> assume each queue's instance would bring its own independent set of 1024 bins?
good thought
>> 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?
>
> Maybe switch to a simpler pure per-flow isolation mode than the default triple-isolate?
>
> BTW what kind of uplink capacity will you use?
last year we had something around 500Mb, they are in the process of changing
ISPs and we may get a bit more, but probably still under 1G
hotel and conference center Internet connections are far smaller than most
people think.
David Lang
next prev parent reply other threads:[~2025-09-28 12:18 UTC|newest]
Thread overview: 8+ 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 [this message]
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
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=alpine.DEB.2.02.2509280513450.14652@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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