From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>
Subject: Re: [Bloat] taking apart BBR's behaviors in flent
Date: Wed, 21 Sep 2016 17:09:18 -0700 [thread overview]
Message-ID: <CAA93jw4o-Q9hH9m36Z+WquiD+uRiwqrBw1UEP1pdCCqtR_qTjA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Y=6rJKuFK3N5zMpw-LrMz4ta1jB6UD2Cg07xw8OfQpg@mail.gmail.com>
I have pushed an updated set of bbr verses cubic tests (formerly
cake/fq_codel/pie/bfifo_256/cake_flowblind) now including pfifo_100,
pfifo_1000, and a CMTS/cable modem emulation that dates back to the
network conditions we had in 2011: 20Mbit down, 5Mbit up, when the
bufferbloat project began.
http://blog.cerowrt.org/flent/bbr-comprehensive.tgz
I note that my conditions are reversed throughout: "up" is from the
server to the client (20Mbit). Mae Culpa: I dare not change anything
on the clients right now as other testing is going on. So what I'm
measuring and emulating here, is downstream bufferbloat (CMTS to
cablemodem to end user), rather than what Jim Gettys started with
(seeing uplink bloat measured in seconds).
Since 2011, download and upload speeds have improved (I think
100/20Mbit is most common nowadays(?), modem buffering on some models
has declined somewhat, CMTS configurations have got better - but that
emulation remains close to correct and in some cases, is much less
bloated than the results many cable users still get today. I also have
dsl, and other emulations, but I figure this dataset is enough to go
on for a while. (since 2011 Web pages have got "tighter", uTP has
deployed to a larger extent, BQL and other mods to the linux stack are
now common, etc, etc. also)
I did produce a couple graphs.
2011 in all it's cubic bloated glory:
http://blog.cerowrt.org/flent/bbr-comprehensive/bufferbloat_20Mbit_2011_glory_cubic.svg
vs BBR competing with itself:
http://blog.cerowrt.org/flent/bbr-comprehensive/bufferbloat_bbr_2016.svg
And one showing a full fledged simultaneous up/down test with bbr +
cubic on the increasingly misnamed squarewave test.
http://blog.cerowrt.org/flent/bbr-comprehensive/bbr_vs_cubic_20Mbit_cablemodem_emulation.png
I do not have more time or energy to review this further today, nor
look at the captures. Probably. Wet Paint!
Enjoy the data. Happy graphing!
PS: one hysterical thing that happened: when I'd started pushing this
data to my git repository and website, I'd forgotten I'd left the
cable modem emulation on and rtt 48 stuff enabled - as well as cubic -
and I had to endure watching the darn thing slow, stop, resume in a
burst, and so on, for what felt like ages.
next prev parent reply other threads:[~2016-09-22 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 19:25 Dave Taht
2016-09-21 19:45 ` [Bloat] [bbr-dev] " Neal Cardwell
2016-09-22 0:09 ` Dave Taht [this message]
2016-09-22 12:09 ` [Bloat] " Alan Jenkins
2016-09-26 19:03 ` [Bloat] [bbr-dev] " Neal Cardwell
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4o-Q9hH9m36Z+WquiD+uRiwqrBw1UEP1pdCCqtR_qTjA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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