From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
"aqm@ietf.org" <aqm@ietf.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] TCP BBR paper is now generally available
Date: Fri, 2 Dec 2016 23:40:06 +0100 [thread overview]
Message-ID: <20161202224006.GA5065@sesse.net> (raw)
In-Reply-To: <CADVnQymCmQ_MWSRcd+Y4=pgf3Shqnw5SfXrAkjonj+UFqtBrdA@mail.gmail.com>
On Fri, Dec 02, 2016 at 05:22:23PM -0500, Neal Cardwell wrote:
> Of course, if we find important use cases that don't work with BBR, we will
> see what we can do to make BBR work well with them.
I have one thing that I _wonder_ if could be BBR's fault: I run backup over
SSH. (That would be tar + gzip + ssh.) The first full backup after I rolled
out BBR on the server (the one sending the data) suddenly was very slow
(~50 Mbit/sec); there was plenty of free I/O, and neither tar nor gzip
(well, pigz) used a full core. My only remaining explanation would be that
somehow, BBR didn't deal well with the irregular stream of data coming from
tar. (A wget between the same machines at the same time gave 6-700 Mbit/sec.)
I will not really blame BBR here, since I didn't take a tcpdump or have time
to otherwise debug properly (short of eliminating the other things I already
mentioned); most likely, it's something else. But if you've ever heard of
others with similar issues, consider this a second report. :-)
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-12-02 22:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 15:52 Dave Taht
2016-12-02 19:15 ` Aaron Wood
2016-12-02 20:32 ` Jonathan Morton
2016-12-02 22:22 ` Neal Cardwell
2016-12-02 22:40 ` Steinar H. Gunderson [this message]
2016-12-02 23:31 ` Eric Dumazet
2016-12-03 13:03 ` Neal Cardwell
2016-12-03 19:13 ` Steinar H. Gunderson
2016-12-03 20:20 ` Eric Dumazet
2016-12-03 20:26 ` Jonathan Morton
2016-12-03 21:07 ` Eric Dumazet
2016-12-03 21:34 ` Steinar H. Gunderson
2016-12-03 21:50 ` Eric Dumazet
2016-12-03 22:13 ` Steinar H. Gunderson
2016-12-03 22:55 ` Eric Dumazet
2016-12-03 23:02 ` Eric Dumazet
2016-12-03 23:09 ` Eric Dumazet
2016-12-03 23:03 ` Steinar H. Gunderson
2016-12-03 23:15 ` Eric Dumazet
2016-12-03 23:24 ` Eric Dumazet
2016-12-04 3:18 ` Neal Cardwell
2016-12-04 8:44 ` Steinar H. Gunderson
2016-12-04 17:13 ` Eric Dumazet
2016-12-04 17:38 ` Steinar H. Gunderson
2016-12-06 17:20 ` Steinar H. Gunderson
2016-12-06 21:31 ` Neal Cardwell
2016-12-03 21:38 ` Jonathan Morton
2016-12-03 21:33 ` Steinar H. Gunderson
2016-12-07 16:28 ` Alan Jenkins
2016-12-07 16:47 ` Steinar H. Gunderson
2016-12-07 17:03 ` Alan Jenkins
2016-12-08 8:24 ` Mikael Abrahamsson
2016-12-08 13:22 ` Dave Täht
2016-12-08 14:01 ` Mikael Abrahamsson
2016-12-08 21:29 ` Neal Cardwell
2016-12-08 22:31 ` Yuchung Cheng
2016-12-09 14:52 ` Klatsky, Carl
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=20161202224006.GA5065@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=ncardwell@google.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