From: David Lang <david@lang.hm>
To: Colin_Higbie <CHigbie1@Higbie.name>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Bufferbloat cure question
Date: Wed, 31 Dec 2025 17:13:50 -0700 (MST) [thread overview]
Message-ID: <sosn6297-np2s-4pr0-q2rq-n16n810476n2@ynat.uz> (raw)
In-Reply-To: <BN7PPF7A8514BADF1FF90D4D0A9172A28FDF1BDA@BN7PPF7A8514BAD.namprd16.prod.outlook.com>
Colin_Higbie wrote:
> At 300Mbps or higher, bufferbloat and jitter skyrocket to hundreds of ms, much
> worse than not using CAKE at all. I can see one of the 4 router CPU cores
> spikes to 100% at those transfer rates whenever I don't limit bandwidth to
> something below 280Mbps.
I know I've seen some patches going past in the last couple of months to let
cake use more than one CPU, so you may want to look at testing those.
it's not uncommon for access points to run out of CPU when processing large
packet volumes (with or without cake), the wndr3700/3800 series that we started
with on the bufferbloat project would run out of steam at about that speed
without any traffic shaping at all.
it's not just a matter of cpu cycles, it also starts to hit memory and MIC
connection limits.
you may be able to get to high speeds if you don't try to have Cake completely
eliminate the effect of bloat, just mitigate it to an acceptale level.
Unfortunantly, I don't know of anyone doing any benchmark testing of routers.
This isn't just a problem at the low end, It's an industry joke that Cisco speed
ratings are "we guarantee that no matter what you do you will never go faster
than this", and that real performance can be as bad as 10% of what the speed
ratings list.
David Lang
next prev parent reply other threads:[~2026-01-01 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176388152155.1303.12028700061090443748@gauss>
2025-12-31 22:19 ` [Starlink] Bufferbloat cure question Colin_Higbie
2025-12-31 23:18 ` [Starlink] " Sebastian Moeller
2026-01-01 0:13 ` David Lang [this message]
2026-01-02 18:21 ` Toke Høiland-Jørgensen
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sosn6297-np2s-4pr0-q2rq-n16n810476n2@ynat.uz \
--to=david@lang.hm \
--cc=CHigbie1@Higbie.name \
--cc=starlink@lists.bufferbloat.net \
/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