From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] building on BDP
Date: Thu, 26 Dec 2019 18:09:22 -0800 [thread overview]
Message-ID: <CAA93jw65TgyF0SWHv=yOJ6VNuUUKbO_3+A1S8Y5un1z5cCJ6dQ@mail.gmail.com> (raw)
At the stanford buffer-sizing workshop the endless subject of bdp came
up - vs 1bdp and s1/qrt(flows)
In looking over this ..
https://datatracker.ietf.org/meeting/105/materials/slides-105-tsvwg-sessa-61-some-congestion-experienced-00
We're just "used" to a baseline figure in between those and also in no
longer riding the sawtooth on *our* fq'd systems, 'round here.
It struck me how much our codel and fq_codel results (since 2012),
differed from both of theirs and from common industry understandings.
We have amassed so much data over time at so many RTTs that pulling
out the actual BDP's (and how long we have them as "bursts") - might
be useful in terms of restructuring that debate.
Another thing on my todo list is how much BBR and BBRv2 hit fq_codel's
current assumptions. I have a feeling codel is overly aggressive in a
range of rtts (or rather bbr makes a bdp assumption that does not hold
for codel'd networks)
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
reply other threads:[~2019-12-27 2:09 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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw65TgyF0SWHv=yOJ6VNuUUKbO_3+A1S8Y5un1z5cCJ6dQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=ecn-sane@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