General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: grenville armitage <garmitage@swin.edu.au>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] TEACUP -- automating TCP experiments on small testbeds
Date: Thu, 16 Apr 2015 11:12:21 +1000	[thread overview]
Message-ID: <552F0C75.6000303@swin.edu.au> (raw)

All,

(Apologies to those who have already seen this elsewhere...)

There is a chance some people doing TCP & bufferbloat experiments might find the following tool useful:

http://caia.swin.edu.au/tools/teacup

We built TEACUP (TCP Experiment Automation Controlled Using Python) to automate many aspects of running TCP performance experiments in our small, specially-constructed physical testbed. TEACUP enables repeatable testing of different TCP algorithms over a range of emulated network path conditions, bottleneck rate limits and bottleneck queuing disciplines.

A key caveat: TEACUP assumes your physical testbed is a multi-host/single-bottleneck dumbbell-like topology with suitably configured end hosts and Linux-based bottleneck router. TEACUP does not try to run experiments over arbitrary network paths or the wider Internet (it is not netperf-wrapper). This has satisfied our use-cases, but YMMV :-)

We've released TEACUP v0.9 publicly in case it may be useful to other researchers who already have (or are interested in setting up) similar network testbeds.

cheers,
gja


                 reply	other threads:[~2015-04-16  1:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=552F0C75.6000303@swin.edu.au \
    --to=garmitage@swin.edu.au \
    --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