From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: David Reed <dpreed@reed.com>, bloat <bloat@lists.bufferbloat.net>,
Jonathan Morton <chromatix99@gmail.com>,
Ketan Kulkarni <ketkulka@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] Bechtolschiem
Date: Fri, 2 Jul 2021 09:59:24 -0700 [thread overview]
Message-ID: <20210702095924.0427b579@hermes.local> (raw)
In-Reply-To: <CAA93jw5gT=9bHG_vmC_kKs6U-brhrvi5Abqe9cJrgYuH5Aoi3A@mail.gmail.com>
On Fri, 2 Jul 2021 09:42:24 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> "Debunking Bechtolsheim credibly would get a lot of attention to the
> bufferbloat cause, I suspect." - dpreed
>
> "Why Big Data Needs Big Buffer Switches" -
> http://www.arista.com/assets/data/pdf/Whitepapers/BigDataBigBuffers-WP.pdf
>
Also, a lot depends on the TCP congestion control algorithm being used.
They are using NewReno which only researchers use in real life.
Even TCP Cubic has gone through several revisions. In my experience, the
NS-2 models don't correlate well to real world behavior.
In real world tests, TCP Cubic will consume any buffer it sees at a
congested link. Maybe that is what they mean by capture effect.
There is also a weird oscillation effect with multiple streams, where one
flow will take the buffer, then see a packet loss and back off, the
other flow will take over the buffer until it sees loss.
next prev parent reply other threads:[~2021-07-02 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55fdf513-9c54-bea9-1f53-fe2c5229d7ba@eggo.org>
[not found] ` <871t4as1h9.fsf@toke.dk>
[not found] ` <3D32F19B-5DEA-48AD-97E7-D043C4EAEC51@gmail.com>
[not found] ` <alpine.DEB.2.02.1606062029380.28955@uplift.swm.pp.se>
[not found] ` <CAD6NSj6vA=bjHt3Txyw8VuV9tqg-A7wvLd6ovJG4Jxabvvjw4g@mail.gmail.com>
[not found] ` <1465267957.902610235@apps.rackspace.com>
2021-07-02 16:42 ` Dave Taht
2021-07-02 16:59 ` Stephen Hemminger [this message]
2021-07-02 17:50 ` Dave Collier-Brown
2021-07-02 19:46 ` Matt Mathis
2021-07-07 22:19 ` [Bloat] Abandoning Window-based CC Considered Harmful (was Re: Bechtolschiem) Bless, Roland (TM)
2021-07-07 22:38 ` Matt Mathis
2021-07-08 11:24 ` Bless, Roland (TM)
2021-07-08 13:29 ` Matt Mathis
2021-07-08 14:05 ` Bless, Roland (TM)
2021-07-08 14:40 ` Jonathan Morton
2021-07-08 20:14 ` [Bloat] [Cerowrt-devel] " David P. Reed
2021-07-09 7:10 ` Erik Auerswald
2021-07-08 13:29 ` [Bloat] " Neal Cardwell
2021-07-08 14:28 ` Bless, Roland (TM)
2021-07-08 15:47 ` Neal Cardwell
2021-07-02 20:28 ` [Bloat] Bechtolschiem Jonathan Morton
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=20210702095924.0427b579@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=dpreed@reed.com \
--cc=ketkulka@gmail.com \
/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