From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "David P. Reed" <dpreed@deepplum.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Thu, 28 Sep 2023 15:33:11 +0300 [thread overview]
Message-ID: <79EC8CB2-0912-4D66-9FA3-990E9C38C281@gmail.com> (raw)
In-Reply-To: <B892D72D-0198-454B-BC15-170B22829351@gmx.de>
> On 28 Sep, 2023, at 3:15 pm, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> This promises even better performance for loads like cake than the already pretty nifty pi4B
Well, increased computing performance is always welcome - but as I've said before, in most cases I don't think CPU performance is the limiting factor for CAKE.
When the CPU load goes up as networking throughput reaches the physical limit of the interface (or the I/O subsystem), what you're seeing is the CPU just spinning its wheels while waiting for a mutex to unblock. Spinning faster doesn't make the mutex unblock sooner!
- Jonathan Morton
next prev parent reply other threads:[~2023-09-28 12:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 1:05 Dave Taht
2023-09-18 1:25 ` Jonathan Morton
2023-09-18 16:57 ` David P. Reed
2023-09-18 19:50 ` dave seddon
2023-09-18 20:24 ` David P. Reed
2023-09-18 22:07 ` Jonathan Morton
2023-09-28 11:44 ` Jonathan Morton
2023-09-28 12:15 ` Sebastian Moeller
2023-09-28 12:33 ` Jonathan Morton [this message]
2023-09-28 12:56 ` David Lang
2023-09-28 13:08 ` Sebastian Moeller
2023-09-28 13:19 ` David Lang
2023-09-28 13:27 ` Sebastian Moeller
2023-10-13 15:59 ` dave seddon
2023-10-13 17:25 ` dave seddon
2023-10-15 15:11 ` dave seddon
2023-10-15 15:52 ` Sebastian Moeller
2023-10-15 16:24 ` dave seddon
2023-10-15 20:29 ` David P. Reed
2023-10-16 3:52 ` Jonathan Morton
2023-10-15 15:53 ` Dave Taht
2023-10-23 20:31 ` dave seddon
2023-10-23 20:35 ` dave seddon
2023-10-24 16:27 ` dave seddon
2023-10-24 21:35 ` dave seddon
2023-10-24 22:06 ` Dave Taht
2023-09-18 22:13 ` Jonathan Morton
2023-09-18 22:52 ` dave seddon
2023-09-18 23:08 ` Jonathan Morton
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=79EC8CB2-0912-4D66-9FA3-990E9C38C281@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--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