From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Fwd: [Bloat] dropbox, bbr and ecn packet capture
Date: Wed, 13 May 2020 18:00:17 -0700 [thread overview]
Message-ID: <CAA93jw6CzE=zJgy0c9Fv0i-+GH-xEeA+M5qC0BERRKcnv5te1Q@mail.gmail.com> (raw)
In-Reply-To: <F8C83786-BC82-4918-973F-DCF3EE32A583@gmail.com>
this was a nice bbr patch
https://lore.kernel.org/netdev/20190123200454.260121-3-priyarjha@google.com/#t
---------- Forwarded message ---------
From: Alexey Ivanov <savetherbtz@gmail.com>
Date: Sun, Apr 26, 2020 at 4:33 PM
Subject: Re: [Bloat] dropbox, bbr and ecn packet capture
To: Neal Cardwell <ncardwell@google.com>
Cc: Jonathan Morton <chromatix99@gmail.com>, ECN-Sane
<ecn-sane@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Yep these are BBRv1 nodes with an older kernel (without even wifi
patches[1]) so their TCP performance is quite suboptimal.
Once we update Edge to 5.4 we'll start the global BBRv2 rollout to all
PoPs. In the mean time, when you hit www.dropbox.com you should
expect (with a very high probability) that you are hitting a BBRv1
endpoint.
[1] https://lore.kernel.org/netdev/20190123200454.260121-3-priyarjha@google.com/#t
--
t: @SaveTheRbtz
> On Apr 25, 2020, at 8:10 PM, Neal Cardwell via Bloat <bloat@lists.bufferbloat.net> wrote:
>
>
> From: Neal Cardwell <ncardwell@google.com>
> Subject: Re: [Bloat] dropbox, bbr and ecn packet capture
> Date: April 25, 2020 at 8:10:11 PM PDT
> To: Jonathan Morton <chromatix99@gmail.com>
> Cc: Dave Taht <dave.taht@gmail.com>, ECN-Sane <ecn-sane@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
>
>
>
>
> On Sat, Apr 25, 2020 at 8:52 PM Jonathan Morton <chromatix99@gmail.com> wrote:
> > On 26 Apr, 2020, at 3:36 am, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I just did a rather large dropbox download. They are well known to be
> > using bbr and experimenting with bbrv2. So I fired off a capture
> > during a big dropbox download...
> >
> > It negotiated ecn, my fq_codel shaper and/or my newly ath10k
> > fq_codel's wifi exerted CE, osx sent back ecn-echo, and the rtt
> > results were lovely. However, there is possibly not a causal
> > relationship here, and if anyone is bored and wants to scetrace,
> > tcptrace or otherwise tear this cap apart, go for it.
>
> Well, the CE response at their end is definitely not Multiplicative Decrease. I haven't dug into it more deeply than that. But they're also not running AccECN, nor are they "proactively" sending CWR to get a "more accurate" CE feedback. I suspect they're running BBRv1 in this one.
>
> Agreed, that looks like BBRv1. I see a few BBRv1 PROBE_RTT phases in there.
>
> Thanks for the trace!
>
> best,
> neal
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
parent reply other threads:[~2020-05-14 1:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <F8C83786-BC82-4918-973F-DCF3EE32A583@gmail.com>]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6CzE=zJgy0c9Fv0i-+GH-xEeA+M5qC0BERRKcnv5te1Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@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