From: Jonathan Morton <chromatix99@gmail.com>
To: dave seddon <dave.seddon.ca@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Tue, 19 Sep 2023 02:08:22 +0300 [thread overview]
Message-ID: <E11A4B01-72A9-4565-A9DF-FDA8D3ACC0D0@gmail.com> (raw)
In-Reply-To: <CANypexSy_uajdqOsEjsC7+nYeUz03V272SKR4af6PT7QtYMeSQ@mail.gmail.com>
> On 19 Sep, 2023, at 1:52 am, dave seddon <dave.seddon.ca@gmail.com> wrote:
>
> I'd love to understand the difference between the tests I've been doing and your tests.
> • How many TCP flows did you have please ( cake performance seems to drop significantly with increased number of TCP flows, although I need to do more testing to understand why )?
It's almost certainly related to the extremely tight AQM settings you imposed on it, and on no other AQM you tested.
> • What was the RTT?
I think this was just in a LAN environment, to gauge the capabilities of the machine just as you're doing. We insert a delay in the middle when testing other things, such as the performance and fine-scale behaviour of a qdisc/CC combination.
> • Load tool?
I believe Pete was using iperf3 for this, or possibly Flent which delegates to netperf. These days he's developing something new along the same lines.
A simple test using one or more of Flent's standard tests should be enough to replicate these results, at least approximately. I would also recommend using ECN, but you should get at least reasonable results without it, provided the AQM is set sanely.
- Jonathan Morton
prev parent reply other threads:[~2023-09-18 23:08 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
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 [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/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=E11A4B01-72A9-4565-A9DF-FDA8D3ACC0D0@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.seddon.ca@gmail.com \
/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