From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: jonathan.kua@deakin.edu.au, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Understanding the Achieved Rate Multiplication Effect in FlowQueue-based AQM Bottleneck
Date: Sat, 4 Dec 2021 10:44:42 -0800 [thread overview]
Message-ID: <CAA93jw6GeQxF59zX=Co1t_28CxLhi6M_Rn=TBYK8sZtRV1enQQ@mail.gmail.com> (raw)
In-Reply-To: <0A6AB0B7-E010-42E3-BAEE-FCBFA5995117@gmail.com>
It was the conquest tool they referenced that really caught my eye
https://www.youtube.com/watch?v=Q3FFzB0SUjc
"ConQuest: Fine-Grained Queue Measurement in the Data Plane"
On Fri, Dec 3, 2021 at 4:09 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 4 Dec, 2021, at 12:27 am, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > https://jonathankua.github.io/preprints/jkua-ieeelcn2021_understanding_ar_preprint-20jul2021.pdf
> >
> > I would love it if somehow the measured effects of chunklets against cake's per-host/per flow fq was examined one day.
>
> I haven't actually measured it, but based on what the above paper says, I can make some firm predictions:
>
> 1: When competing against traffic to the same local host, the performance effects they describe will be present.
>
> 2: When competing against traffic to a different local-network host, the performance effects they describe will be attenuated or even entirely absent.
>
> 3: They noted one or two cases of observable effects of hash collisions in their tests with FQ-Codel. These will be greatly reduced in prevalence with Cake, due to the set-associative hash function which specifically addresses that phenomenon.
>
> - Jonathan Morton
--
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
next prev parent reply other threads:[~2021-12-04 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 22:27 Dave Taht
2021-12-04 0:09 ` Jonathan Morton
2021-12-04 18:44 ` Dave Taht [this message]
2021-12-04 22:29 ` David P. Reed
2021-12-05 1:20 ` Dave Taht
2021-12-04 23:01 ` David P. Reed
2021-12-05 1:24 ` Dave Taht
2021-12-07 20:04 ` David P. Reed
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='CAA93jw6GeQxF59zX=Co1t_28CxLhi6M_Rn=TBYK8sZtRV1enQQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=jonathan.kua@deakin.edu.au \
/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