From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Tue, 28 Jul 2015 21:10:08 +0100 [thread overview]
Message-ID: <55B7E1A0.6010101@gmail.com> (raw)
In-Reply-To: <87wpxkozk3.wl-jch@pps.univ-paris-diderot.fr>
On 28/07/15 20:24, Juliusz Chroboczek wrote:
>> I would be very interested in flent benchmarks of your 3g device with
>> the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
>> rrul_be tests.
> Please send me detailed instructions, as well as information about how
> much traffic I'm going to have to pay for.
>
> FWIW, the RTT of the (unloaded) link varies tremendously. Right now
> (around 21:20), I'm seeing 89ms to 823ms, with an average of 192ms and
> a standard deviation of 146ms. It's better at night, mid-morning it's
> pretty much unusable.
>
> -- Juliusz
It's a straightforward usage. My one concern would be ensuring you have
netperf (netperf.org) built as required.
I suggest building netperf from source. (Cite: flent requirements[1],
and experience of failures with the Debian package)
./configure --enable-demo=yes --enable-histogram
make
sudo make install
Untested (on my part) but documented[2] install is by debs at
https://software.opensuse.org/download.html?project=home:tohojo:flent&package=flent
or "pip install flent".
flent defaults to a 60 second test (and will run at whatever 4x tcp
streams can manage). Given the variation & high rtt I wouldn't want to
shorten that very much. One available graph from the output file will
be what I assume Dave means when he says "mountain plot". That is,
bandwidth & latency v.s. time.
Assuming EU (server taken from
https://github.com/richb-hanover/CeroWrtScripts):
flent -H netperf-eu.bufferbloat.net rrul -t
my-little-3G-connection-on-fq_codel
rrul is the test. The -t value provides a caption. Move the output
file it mentions from /tmp (huh?) to somewhere more useful. View
available graphs with flent --gui <file>.
Alan
[1]
http://netoptimizer.blogspot.co.uk/2014/09/mini-tutorial-for-netperf-wrapper-setup.html
[2] https://github.com/tohojo/flent/blob/master/README.rst
additional ref, including using your own server for netperf instead:
https://flent.org/intro.html#quick-start
next prev parent reply other threads:[~2015-07-28 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:09 Juliusz Chroboczek
2015-07-28 13:33 ` Toke Høiland-Jørgensen
2015-07-28 13:50 ` Juliusz Chroboczek
2015-07-28 14:05 ` Toke Høiland-Jørgensen
2015-07-28 14:11 ` Simon Barber
2015-07-28 14:21 ` Eric Dumazet
2015-07-28 14:31 ` Simon Barber
2015-07-28 14:43 ` Jonathan Morton
2015-07-28 14:49 ` Eric Dumazet
2015-07-28 14:55 ` Eric Dumazet
2015-07-28 16:02 ` Alan Jenkins
2015-07-28 16:22 ` Sebastian Moeller
2015-07-28 17:11 ` Michael Welzl
2015-07-29 7:19 ` David Lang
2015-07-28 19:20 ` Juliusz Chroboczek
2015-07-28 19:29 ` Alan Jenkins
2015-07-28 14:18 ` Eric Dumazet
2015-07-28 14:44 ` Dave Taht
2015-07-28 14:52 ` Eric Dumazet
2015-07-28 19:24 ` Juliusz Chroboczek
2015-07-28 19:31 ` Bill Ver Steeg (versteb)
2015-07-28 20:10 ` Alan Jenkins [this message]
2015-07-28 20:45 ` Alan Jenkins
2015-07-29 13:15 ` Stefan Alfredsson
2015-07-29 13:41 ` 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/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=55B7E1A0.6010101@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jch@pps.univ-paris-diderot.fr \
/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