From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
codel@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] RFC: Realtime Response Under Load (rrul) test specification
Date: Tue, 6 Nov 2012 13:42:04 +0100 [thread overview]
Message-ID: <CAA93jw7kpMRkjQzaUsnd8mUHuimAZqZynfdVfV_gMRJ5ueSiTA@mail.gmail.com> (raw)
I have been working on developing a specification for testing networks
more effectively for various side effects of bufferbloat, notably
gaming and voip performance, and especially web performance.... as
well as a few other things that concerned me, such as IPv6 behavior,
and the effects of packet classification.
A key goal is to be able to measure the quality of the user experience
while a network is otherwise busy, with complex stuff going on in the
background, but with a simple presentation of the results in the end,
in under 60 seconds.
While it's not done yet, it escaped into the wild today, and I might
as well solicit wider opinions on it, sooo... get the spec at:
https://github.com/dtaht/deBloat/blob/master/spec/rrule.doc?raw=true
Portions of the test are being prototyped in the netperf-wrappers repo
on github. The initial results of the rrul test on several hotel
networks I've tried it on are "interesting". Example:
http://www.teklibre.com/~d/rrul2_conference.pdf
A major sticking point at the moment is to come up with an equivalent
of the chrome-benchmarks for measuring relative web page performance
with and without a network load, or to merely incorporate some
automated form of that benchmark into the overall test load.
The end goal is to have a complex, comprehensive benchmark of some
core networking issues, that produces simple results, whether they be
via a java tool like icsi's, or via flash on the web, or the command
line, via something like netperf.
Related resources:
netperf 2.6 or later running on a fairly nearby server
https://github.com/tohojo/netperf-wrapper
python-matplotlib
I look forward to your comments.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2012-11-06 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 12:42 Dave Taht [this message]
2012-11-06 13:42 ` [Cerowrt-devel] [Bloat] " Henrique de Moraes Holschuh
2012-11-06 13:56 ` Dave Taht
2012-11-06 15:40 ` [Cerowrt-devel] [Codel] " Wesley Eddy
2012-11-06 18:58 ` [Cerowrt-devel] " Michael Richardson
2012-11-06 18:14 ` [Cerowrt-devel] [Codel] " Rick Jones
2012-11-09 10:34 ` Dave Taht
2012-11-09 17:57 ` 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/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=CAA93jw7kpMRkjQzaUsnd8mUHuimAZqZynfdVfV_gMRJ5ueSiTA@mail.gmail.com \
--to=dave.taht@gmail.com \
--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