From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass smtp.mailfrom=lang.hm; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from mail.lang.hm (wsip-70-167-213-146.ph.ph.cox.net [70.167.213.146]) by mail.toke.dk (Postfix) with ESMTPS id 1A7D0B3A157 for ; Thu, 01 Jan 2026 01:13:57 +0100 (CET) Received: from [10.2.2.53] (unknown [10.2.2.53]) by mail.lang.hm (Postfix) with ESMTP id 41791215822; Wed, 31 Dec 2025 16:13:55 -0800 (PST) Date: Wed, 31 Dec 2025 17:13:50 -0700 (MST) From: David Lang To: Colin_Higbie cc: "starlink@lists.bufferbloat.net" In-Reply-To: Message-ID: References: <176388152155.1303.12028700061090443748@gauss> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID-Hash: QF2Q4FBOJCSMNKWLNSE2SGF3V6KMRG2H X-Message-ID-Hash: QF2Q4FBOJCSMNKWLNSE2SGF3V6KMRG2H X-MailFrom: david@lang.hm X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Starlink] Re: Bufferbloat cure question List-Id: "Starlink has bufferbloat. Bad." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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