From: Rick Jones <rick.jones2@hp.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Re: RRUL test prototypes
Date: Thu, 03 Jan 2013 12:22:50 -0800 [thread overview]
Message-ID: <50E5E89A.1080200@hp.com> (raw)
In-Reply-To: <CAA93jw5TRQqBh2AuvfU7A2jLyisg3dEjAG6jj2pPDAZLvrmcOg@mail.gmail.com>
On 12/31/2012 03:01 PM, Dave Taht wrote:
> Toke made enormous progress on a RRUL test prototype over the last 2
> months. It requires a recent netperf, python, python's matplotlib, and
> netperf-wrappers.
>
> For basic install on a debian/ubuntu box:
>
> sudo apt-get remove netperf
> svn co http://www.netperf.org/svn/netperf2/trunk/ netperf-2.7
> cd netperf-2.7
strictly speaking I have not declared a netperf-2.7 and at least as I'm
typing am not sure if the current top-of-trunk will become 2.7.0 or
2.6.1 (I have to see if I've changed the control messages size since 2.6.0)
BTW, in Ubuntu at least I have gotten into the habit of not apt-get
removing the supplied netperf, but sudo service netperf stop instead,
then build my bits and then copy the netperf and netserver binary to
/usr/bin (where Ubuntu puts them) and an sudo service netperf start.
That way I do not have to remember to start a netserver each time I
reboot the OS.
>...
>
> You can also run mtr at the same time in another window to see where
> the bottlenecks are. If you are not based in the US, you should setup
> a netperf netserver nearer by than
> snapon (which is in california) - there's one in germany for example.
I'll mention again just for completeness that a top-of-trunk
netperf/netserver includes support for a required passphrase to be
provided by netperf to netserver to run a test between them. It is
somewhat lame as the passphrase is passed in cleartext, but probably
still better than a wide-open netserver on the Internet.
happy benchmarking,
rick
prev parent reply other threads:[~2013-01-03 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 23:01 Dave Taht
2013-01-03 20:22 ` Rick Jones [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E5E89A.1080200@hp.com \
--to=rick.jones2@hp.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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