From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] exploring a strangeness in a modern tcp and kernel
Date: Mon, 13 Dec 2021 06:47:10 -0800 [thread overview]
Message-ID: <CAA93jw7twPXuPEM=aKYCjF1dcP8Kja0eyDJa=14r_X5=eWZP_g@mail.gmail.com> (raw)
I have been off trying to get good benchmarks of the new mikrotik 7.1
release, which has a working version of cake and fq-codel. Got a very
enthusiastic tester running the "xanmod" kernel which among other
things, has bbrv2 on by default.
Incredibly long, often confusing, and ever growing thread over here:
https://forum.mikrotik.com/viewtopic.php?p=897719#p897629
News so far:
cake doesn't crash - that was my basic objective!! - as it would crash
in mikrotik 7.0. It works great on our basic suite of tests up and
down...
Tons of flent plots vs a vs fq-codel, a fifo, cake, and sfq (sfq is
the goto default in the mikrotik world)
First ever test of BBRv2 vs cake that I know of (we moved back to
cubic later). See pics.
First time I've ever looked at how a bonded dsl connection works
However, after finally getting a packet capture, the *stumper* is that
tests using 8 or more flows actually get capped throughput well below
what the link is capable of, and I have no idea of the cause, as yet.
Up until now I was thinking the aqm was to blame, but...
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2021-12-13 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7twPXuPEM=aKYCjF1dcP8Kja0eyDJa=14r_X5=eWZP_g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rpm@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