General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: erik.taraldsen@telenor.com
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] BBR implementations, knobs to turn?
Date: Mon, 16 Nov 2020 16:14:45 -0500	[thread overview]
Message-ID: <CADVnQykVmQrg_nuSG1XqGUrEKQgaO1+uWmB5SDfeFKkB+G2_FA@mail.gmail.com> (raw)
In-Reply-To: <1605540351240.98589@telenor.com>

[-- Attachment #1: Type: text/plain, Size: 2395 bytes --]

A couple questions:

- I guess this is Linux TCP BBRv1 ("bbr" module)? What's the OS
distribution and exact kernel version ("uname -r")?

- What do you mean when you say "The old server allows for more
re-transmits"?

- If BBRv1 is suffering throughput problems due to high retransmit rates,
then usually the retransmit rate is around 15% or higher. If the retransmit
rate is that high on a radio link that is being tested, then that radio
link may be having issues that should be investigated separately?

- Would you be able to take a tcpdump trace of the well-behaved and
problematic traffic and share the pcap or a plot?

https://github.com/google/bbr/blob/master/Documentation/bbr-faq.md#how-can-i-visualize-the-behavior-of-linux-tcp-bbr-connections

- Would you be able to share the output of "ss -tin" from a recently built
"ss" binary, near the end of a long-lived test flow, for the well-behaved
and problematic cases?

https://github.com/google/bbr/blob/master/Documentation/bbr-faq.md#how-can-i-monitor-linux-tcp-bbr-connections

best,
neal



On Mon, Nov 16, 2020 at 10:25 AM <erik.taraldsen@telenor.com> wrote:

> I'm in the process of replacing a throughput test server.  The old server
> is running a 1Gbit Ethernet card on a 1Gbit link and ubuntu.  The new a
> 10Gbit card on a 40Gbit link and centos.  Both have low load and Xenon
> processors.
>
>
> The purpose is for field installers to verify the bandwidth sold to the
> customers using known clients against known servers.  (4G and 5G fixed
> installations mainly).
>
>
> What I'm finding is that the new server is consistently delivering
> slightly lower throughput than the old server.  The old server allows for
> more re-transmits and has a slightly higher congestion window than the new
> server.
>
>
> Is there any way to tune bbr to allow for more re-transmits (which seems
> to be the limiting factor)?  Or other suggestions?
>
>
>
> (Frankly I think the old server is to aggressive for general purpose use.
> It seems to starve out other tcp sessions more than the new server.  So for
> delivering regular content to users the new implementation seems more
> balanced, but that is not the target here.  We want to stress test the
> radio link.)
>
>
> Regards Erik
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 3664 bytes --]

  reply	other threads:[~2020-11-16 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 15:25 erik.taraldsen
2020-11-16 21:14 ` Neal Cardwell [this message]
2020-11-17 10:05   ` erik.taraldsen
2020-11-17 15:07     ` Jesper Dangaard Brouer
2020-11-19  7:57       ` erik.taraldsen
2020-11-19 13:32         ` Luca Muscariello
2020-11-19 14:35           ` erik.taraldsen
2020-11-20 11:10             ` Jesper Dangaard Brouer
2020-11-20 12:42               ` Toke Høiland-Jørgensen
2020-11-23 12:57                 ` erik.taraldsen
2020-11-30 17:18                   ` Aaron Wood
2020-11-20 23:34       ` 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=CADVnQykVmQrg_nuSG1XqGUrEKQgaO1+uWmB5SDfeFKkB+G2_FA@mail.gmail.com \
    --to=ncardwell@google.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=erik.taraldsen@telenor.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