From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: [Codel] Update of netperf-wrapper testing tool - new features, CDF plots
Date: Mon, 26 Nov 2012 17:33:06 +0100 [thread overview]
Message-ID: <877gp8nx31.fsf@toke.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
Hey everyone
I've just pushed an update to the netperf-wrapper testing tool which
allows several different plots to be created from the same dataset,
including CDF plots from ping times. The reworked configuration file
format also allows for more flexibility in specifying tests (since the
configuration format is now full Python source), which allows more
options to be specified on the command line when running the tests (such
as test length, proper ipv4/6 handling with -4 and -6 parameters, etc).
Test data is now also saved in a json format at each test run (along
with relevant metadata), hopefully making it easier to keep track of
test data, and possibly at some point in the future allowing for
interoperability with other tools.
Get the source from github (https://github.com/tohojo/netperf-wrapper)
and give it a spin. The main test is the rrul stress test (prototyping
Dave's draft specification), but simple one- or two-stream TCP tests are
also available. To get started and run the rrul test, seeing a CDF plot
of the ping times, execute the following commands:
git clone https://github.com/tohojo/netperf-wrapper.git
cd netperf-wrapper
./netperf-wrapper.py -H <netperf server> -p ping_cdf rrul
Provided there's a 'python2' executable available in the PATH, that
matplotlib is installed correctly, and that a netperf built with demo
mode is available, this will run the rrul test and pop up an interactive
plot browser of the results. It will also save the test data in
rrul-<time>.json.gz for later export to csv, plotting etc.
See ./netperf-wrapper.py -h and the README file for further options.
-Toke
--
Toke Høiland-Jørgensen
toke@toke.dk
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
reply other threads:[~2012-11-26 16:33 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gp8nx31.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@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