From: Dave Taht <dave.taht@gmail.com>
To: libreqos@lists.bufferbloat.net
Subject: [LibreQoS] mice and elephants visualizations
Date: Mon, 24 Oct 2022 07:14:15 -0700 [thread overview]
Message-ID: <CAA93jw75U2TzWupfh4AxUfi-NyKud1QMH4zRDzO0z30p=USC0Q@mail.gmail.com> (raw)
All of us, including me! have a tendency to do things like measure a
ton of flent or iperf sessions and consider the end result "good".
Actual traffic looks nothing like that, with the vast majority of
flows in slow start, and ending quickly. This old paper came to mind
yesterday, in light of seeing bracket's qoe stuff land:
http://www.cs.unc.edu/Research/dirt/proj/marron/MiceElephants/
One of fq_codel's and cakes hidden advantages is in the fq portion,
where, for the first 3-5 round trips on a tcp connection,
go out first, and that is in part why it runs circles around everything else.
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-10-24 14:14 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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw75U2TzWupfh4AxUfi-NyKud1QMH4zRDzO0z30p=USC0Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=libreqos@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