From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [bbr-dev] Introducing Transperf
Date: Thu, 26 Sep 2019 12:15:50 -0700 [thread overview]
Message-ID: <CAA93jw4F3jkcC2ESPAE24Z6KQFgimHyMuLB21zaKKeB5c3_9Tw@mail.gmail.com> (raw)
In-Reply-To: <CACSApvZtHJNXu4nAWSekJWE3ZxTtfTiLgtQ+=ASNZOYwOgSnHw@mail.gmail.com>
---------- Forwarded message ---------
From: 'Soheil Hassas Yeganeh' via BBR Development <bbr-dev@googlegroups.com>
Date: Thu, Sep 26, 2019 at 12:10 PM
Subject: [bbr-dev] Introducing Transperf
To: Soheil Hassas Yeganeh <soheil@google.com>
We'd like to announce the availability of transperf: a network
protocol performance testing tool.
transperf enables users to test TCP performance over a variety of
emulated network scenarios (using netem), including RTT, bottleneck
bandwidth, and policed rate that can change over time. The tool
supports testing multiple flows on multiple machines, and can test the
coexistence of multiple congestion control algorithms in a single
test. Users can specify test configurations and make assertions about
the expected results (i.e., goodput, RTTs, retransmit rates, and
fairness) using a Python-based configuration language.
The BBR team at Google has been using transperf for some of our BBR
testing, and many of the pastel bandwidth plots from various BBR IETF
slide decks were produced using this tool. Transperf includes support
for plotting internal state used by the BBRv2 algorithm, and can be
easily extended to support other congestion control algorithms as
well. We have found it useful, and hope others find it useful as well.
The code is released under the Apache-2.0 license, and available in a
git repository at:
https://github.com/google/transperf
The source for transperf is in the git repository, along with example
configuration scripts. It has been tested on Debian 9. We would love
to accept your bug reports, patches, and contributions through GitHub
issues and pull requests.
Co-authored-by: Soheil Yeganeh
Co-authored-by: Arjun Roy
Co-authored-by: Neal Cardwell
Co-authored-by: Luke Hsiao
Co-authored-by: Priyaranjan Jha
Co-authored-by: Haitao Wu
Co-authored-by: Yousuk Seung
Co-authored-by: Kevin(Yudong) Yang
Co-authored-by: Michael McLennan
Co-authored-by: Yuchung Cheng
Co-authored-by: Eric Dumazet
Co-authored-by: Maciej Żenczykowski
--
You received this message because you are subscribed to the Google
Groups "BBR Development" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to bbr-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbr-dev/CACSApvZtHJNXu4nAWSekJWE3ZxTtfTiLgtQ%2B%3DASNZOYwOgSnHw%40mail.gmail.com.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
parent reply other threads:[~2019-09-26 19:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CACSApvZtHJNXu4nAWSekJWE3ZxTtfTiLgtQ+=ASNZOYwOgSnHw@mail.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/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=CAA93jw4F3jkcC2ESPAE24Z6KQFgimHyMuLB21zaKKeB5c3_9Tw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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