From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>,
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: Wed, 7 Dec 2016 16:28:15 +0000 [thread overview]
Message-ID: <83609420-9ab8-666d-8282-e2f22b17d68d@gmail.com> (raw)
In-Reply-To: <20161203191353.GA972@sesse.net>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
On 03/12/16 19:13, Steinar H. Gunderson wrote:
> On Sat, Dec 03, 2016 at 08:03:50AM -0500, Neal Cardwell wrote:
>>> 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.)
>> Thanks for the report, Steinar. This is the first report we've had
>> like this, but it would be interesting to find out what's going
>> on.
>>
>> Even if you don't have time to apply the patches Eric mentions, it
>> would be hugely useful if the next time you have a slow transfer
>> like that you could post a link to a tcpdump packet capture
>> (headers only is best, say -s 120). Ideally the trace would
>> capture a whole connection, so we can see the wscale on the SYN
>> exchange.
>
> I tried reproducing it now. I can't get as far down as 50 Mbit/sec,
> but it stopped around 100 Mbit/sec, still without any clear
> bottlenecks. cubic was just as bad, though.
>
> I've taken two tcpdumps as requested; I can't reboot this server
> easily right now, unfortunately. They are:
>
> http://storage.sesse.net/bbr.pcap -- ssh+tar+gnupg
> http://storage.sesse.net/bbr2.pcap -- wget between same hosts
>
> /* Steinar */
Since no-one's explicitly mentioned this: be aware that SSH is known for
doing application-level windowing, limiting performance.
E.g. see https://www.psc.edu/index.php/hpn-ssh/638
[-- Attachment #2: Type: text/html, Size: 2749 bytes --]
next prev parent reply other threads:[~2016-12-07 16:28 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
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 [this message]
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=83609420-9ab8-666d-8282-e2f22b17d68d@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=ncardwell@google.com \
--cc=sgunderson@bigfoot.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