Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] collecting some data?
Date: Mon, 25 Feb 2013 15:13:15 -0500	[thread overview]
Message-ID: <CAA93jw6F7JTGKymCpvDO2ywj84Ug0ar5Jk4N=zPine5+GOmgnA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2108 bytes --]

I have been collecting statistics on the behavior of the 3.7.5-2 version of
cerowrt, and perhaps y'all out there can help. I've been doing four
repeatable tests.

I feed the attached file into the chrome web page benchmark and run it 4
times:

1) No other load on the system
2) while running a single up and single down netperf stream to icei.org (on
the east coast)
3) then while still loaded, after turning on simple_qos.sh, set for ~85% of
the rated up/down bandwidth...
4) then killing the load, and keeping simple_qos enabled.

I export each detailed (you have to select it) .csv output from that
benchmark to a file.

I do it against a bidirectional stream - one each of

netperf -l 6000 -4 -H icei.org -t TCP_MAERTS &
netperf -l 6000 -4 -H icei.org -t TCP_STREAM &

(if you have ipv6, more power to you, kill the -4. )

then starting the web tests 10-20 seconds later. It's interesting to watch
cero's bandwidth graphs while doing this.

There are netperf servers setup on the east (icei.org) and west coast (
snapon.lab.bufferbloat.net) and a few other places. It would be sane to
setup your own someplace you control (from netperf's svn compiled with
--enable-demo), as it helps to have a shorter RTT to truly load up the
link. You can also run the rrul test (preferably for 5 minutes or more
because this test idea KILLs web page load times) to get a heavier load and
more graphs.

If you are up to trying this test series, please let me know, send along
the details of your setup, and the 4 csv files, and perhaps your data will
show up in an upcoming paper.

The chrome web page benchmark can be had at:

https://chrome.google.com/webstore/detail/page-benchmarker/channimfdomahekjcahlbpccbgaopjll?hl=en

And requires you fire off chrome with --enable-benchmarking

You can use the version of netperf on cerowrt to generate the load if you
like, but rrul doesn't run on that. Latest version of rrul is at
https://github.com/tohojo/netperf-wrapper

-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #1.2: Type: text/html, Size: 2898 bytes --]

[-- Attachment #2: 12.urls --]
[-- Type: application/octet-stream, Size: 302 bytes --]

http://www.google.com,
https://www.facebook.com,
http://www.youtube.com,
http://www.yahoo.com,
http://www.baidu.com,
http://www.wikipedia.org,
http://www.amazon.com,
https://twitter.com,
http://www.bing.com,
http://www.yandex.ru,
http://www.microsoft.com/en-US/default.aspx,
http://xfinity.comcast.net

             reply	other threads:[~2013-02-25 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 20:13 Dave Taht [this message]
2013-02-25 20:22 ` Dave Taht
2013-02-25 20:39 ` Maciej Soltysiak
2013-02-25 20:40   ` Maciej Soltysiak
2013-02-25 20:44   ` Dave Taht

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw6F7JTGKymCpvDO2ywj84Ug0ar5Jk4N=zPine5+GOmgnA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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