From: Rick Jones <rick.jones2@hp.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Codel] better testing, linux 3.6.1, cerowrt credits, other stuff
Date: Tue, 09 Oct 2012 09:45:30 -0700 [thread overview]
Message-ID: <507454AA.9060206@hp.com> (raw)
In-Reply-To: <87d30rra1s.fsf@toke.dk>
Toke -
The script looks reasonable. Certainly cleaner than any Python I've yet
written :) I might be a little worried about skew error though (assuming
I've not mis-read the script and example ini file). That is why I use
the "demo mode" of netperf in
http://www.netperf.org/svn/netperf2/trunk/doc/examples/bloat.sh though
it does make the post-processing rather more involved.
I see you are running the TCP_RR test for less time than the
TCP_STREAM/TCP_MAERTS test. What do you then do to show the latency
without the bulk transfer load?
You may find
http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html#Omni-Output-Selection
in 2.5.0 and 2.6.0 helpful when it comes to getting netperf to emit
specific measurements.
I was thinking of trying to write a version of bloat.sh in python but
before I did I wanted to know if python was sufficiently available in
most folks bufferbloat testing environments. I figure in
"full-featured" *nix systems that isn't an issue, but what about in the
routers?
happy benchmarking,
rick jones
here are some links concerning demo mode:
http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html#Using-_002d_002denable_002ddemo
http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html#index-g_t_002dD_002c-Global-22
next prev parent reply other threads:[~2012-10-09 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 3:21 [Bloat] " Dave Taht
2012-10-09 14:31 ` Toke Høiland-Jørgensen
2012-10-09 16:45 ` Rick Jones [this message]
2012-10-09 18:28 ` [Bloat] [Codel] " Dave Taht
2012-10-09 19:35 ` Toke Høiland-Jørgensen
2012-10-09 20:05 ` Rick Jones
2012-10-10 14:27 ` Toke Høiland-Jørgensen
2012-10-10 23:27 ` Michael Richardson
2012-10-10 23:29 ` Stephen Hemminger
2012-10-10 23:55 ` Luigi Rizzo
2012-10-10 23:32 ` Rick Jones
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=507454AA.9060206@hp.com \
--to=rick.jones2@hp.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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