General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: dave seddon <dave.seddon.ca@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Frantisek Borsik <frantisek.borsik@gmail.com>,
	codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>,
	Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	ryan@rkhtech.org
Subject: [Bloat] Re: [Cake] Re: Re: CAKE-MQ merged to OpenWrt 25.12 today (February 15)
Date: Mon, 23 Feb 2026 11:18:37 +0100	[thread overview]
Message-ID: <87o6lfoj9e.fsf@toke.dk> (raw)
In-Reply-To: <CANypexSZPx38m59j5=CrOkA_S7=XaJJhZ9-jh0ex5i8pJjeDYg@mail.gmail.com>

dave seddon <dave.seddon.ca@gmail.com> writes:

> Thanks for the replies guys.
>
> I'm using a desktop class machine with a Ryzen Threadripper PRO 3945WX
> (12 cores/24 threads).  - It's really not fast enough for what I was
> attempting.  When you are used to using more powerful machines at
> work, it's easy to forget how powerful server class machines are.
>
> I tried creating many flows using a combination of tools, but this
> just saturates all the cores, causing RTTs to spike due to CPU
> contention.  The idea was to simulate lots of flows like you might
> have at a conference, but I'm going to need more and more powerful
> machines.
>
> This is the mq-cake config
>
>   Flows: fping=1, iperf2=300, wrk=100, dnsperf=20, flent=1, crusader=1
>   Qdisc: mq-cake
>     ixgbe0:
>       qdisc mq 1: root
>       qdisc cake 8005: parent 1:3 bandwidth 10Gbit diffserv4
> triple-isolate nat wash no-ack-filter split-gso rtt 100ms raw overhead
> 0

[...]

Erm, why this setup? You're asking each instance of cake to shape at
10Gbit (on a single CPU), for a total bandwidth of 80 Gbit. Multi-queue
shaping with cake is exactly the use case that the cake_mq qdisc is
meant to be used for, so try that?

-Toke

      reply	other threads:[~2026-02-23 10:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-15 17:42 [Bloat] CAKE-MQ merged to OpenWrt 25.12 today (February 15) Frantisek Borsik
2026-02-16 16:51 ` [Bloat] Consumer CPE with Modern AQM? Livingood, Jason
2026-02-16 17:24   ` [Bloat] " Frantisek Borsik
2026-02-16 17:45   ` Daniel Sterling
2026-02-16 20:10     ` David Collier-Brown
2026-02-17  4:12     ` Jim Gettys
2026-02-17 12:12       ` Jan Ceuleers
2026-02-17 16:35       ` [Bloat] Re: [EXTERNAL] " Livingood, Jason
2026-02-17 16:24     ` [Bloat] Re: [EXTERNAL] " Livingood, Jason
2026-02-17  6:10 ` [Bloat] Re: [Cake] CAKE-MQ merged to OpenWrt 25.12 today (February 15) dave seddon
2026-02-17  6:41   ` Stephen Hemminger
2026-02-17 13:23   ` Toke Høiland-Jørgensen
2026-02-17 14:34     ` [Bloat] Re: [Cake] Re: " Stephen Hemminger
2026-02-17 16:32       ` Toke Høiland-Jørgensen
2026-02-17 16:55         ` Jonas Köppeler
2026-02-20 15:59         ` dave seddon
2026-02-23 10:18           ` Toke Høiland-Jørgensen [this message]

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=87o6lfoj9e.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.seddon.ca@gmail.com \
    --cc=frantisek.borsik@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=ryan@rkhtech.org \
    --cc=stephen@networkplumber.org \
    /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