Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
	 BBR Development <bbr-dev@googlegroups.com>,
	flent-users <flent-users@flent.org>
Subject: Re: [Ecn-sane] [bbr-dev] duplicating the BBRv2 tests at iccrg in flent?
Date: Fri, 5 Apr 2019 12:58:06 -0400	[thread overview]
Message-ID: <CADVnQy=tiUSj5ubHWine+65yk2BK3nMts4eTzzE1o0T-9uN+2g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6HUzjq1Rk9OsqXRuWze3tzXfhz1p3promaD_Zx1Xbdbw@mail.gmail.com>

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

On Fri, Apr 5, 2019 at 11:51 AM Dave Taht <dave.taht@gmail.com> wrote:

>
> Was GRO/GSO enabled on the router? host? server?
>

In this particular invocation of this particular test, the sender,
receiver, and router functionality were all running on the same machine,
using network namespaces and veth devices; TSO and GRO were enabled.


> >
> >>
> >> 5) What was the result with fq_codel instead?
> >
> >
> > With fq_codel and the same ECN marking threshold (fq_codel ce_threshold
> 242us), we see slightly smoother fairness properties (not surprising) but
> with slightly higher latency.
> >
> > The basic summary:
> >
> > retransmits: 0
> > flow throughput: [46.77 .. 51.48]
> > RTT samples at various percentiles:
> >   %   | RTT (ms)
> > ------+---------
> >    0    1.009
> >   50    1.334
> >   60    1.416
> >   70    1.493
> >   80    1.569
> >   90    1.655
> >   95    1.725
> >   99    1.902
> >   99.9  2.328
> >  100    6.414
>
> This is lovely. Is there an open source tool you are using to generate
> this from the packet capture? From wireshark? Or is this from sampling
> the TCP_INFO parameter of netperf?


Thanks. The results and bandwidth graphs are from an internal test
orchestration/evaluation/visualization tool written a few years ago by our
BBR team member, Soheil Hassas Yeganeh, and further enhanced by others on
our team over the years. We are trying to find the time to open-source it,
but haven't yet. It can generate the graphs either from pcap files or "ss"
output. This one was from "ss" output.

neal

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

  reply	other threads:[~2019-04-05 16:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05  7:42 [Ecn-sane] " Dave Taht
2019-04-05 15:10 ` [Ecn-sane] [bbr-dev] " Neal Cardwell
2019-04-05 15:51   ` Dave Taht
2019-04-05 16:58     ` Neal Cardwell [this message]
2019-04-05 16:20   ` Jonathan Morton
2019-04-06 11:56     ` Neal Cardwell
2019-04-06 14:37       ` [Ecn-sane] [Flent-users] " Sebastian Moeller
2019-04-09  1:33         ` Neal Cardwell
2019-04-09  2:09           ` Jonathan Morton
2019-04-09  6:30           ` Sebastian Moeller
2019-04-09 14:33             ` Neal Cardwell
2019-04-09 17:20               ` Sebastian Moeller
2019-04-06 11:49   ` [Ecn-sane] " Dave Taht
2019-04-06 12:31     ` 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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADVnQy=tiUSj5ubHWine+65yk2BK3nMts4eTzzE1o0T-9uN+2g@mail.gmail.com' \
    --to=ncardwell@google.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=flent-users@flent.org \
    /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