I'm not sure why people are focused on iperf as a test of fqcodel.
iperf is a "hot rod" test. The UDP versions ignores congestion signals entirely, and thus is completely irrelevant to bufferbloat.
The TCP tests are focused on throughput only, in an extreme case.
While it might be a nice footnote in a discussion of bufferbloat mitigation to say that "iperf is not too badly affected", the purpose of iperf as a measurement tool has literally NOTHING to do with bufferbloat management.
In fact, the focus on optimizing iperf by a half a percent or so in laboratory conditions is *literally* how we ended up with bufferbloat in the first place.
You don't design a highly maneuverable jet fighter by designing a rocket that goes from point A to point B the fastest.
The Internet was NEVER supposed to support circuit switchable traffic models.
Someone needs to make a tool that measures the right thing - and using iperf is the opposite of the right thing.
-----Original Message-----
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
Sent: Monday, November 26, 2012 6:21pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Paolo Valente" <paolo.valente@unimore.it>, "Eric Raymond" <esr@thyrsus.com>, codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net, "bloat" <bloat@lists.bufferbloat.net>, paulmck@linux.vnet.ibm.com, "David Woodhouse" <dwmw2@infradead.org>, "John Crispin" <blogic@openwrt.org>
Subject: Re: [Cerowrt-devel] FQ_Codel lwn draft article review
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> The latter should be pretty straight forward, I suppose. And if I recall
> correctly, you did want to measure the upstream jitter?
Following up on this, I've created a proof of concept python script that
starts an iperf server in the background, parses the output, and
presents a command line interface that dumps the parsed data in json
format when asked for a transfer ID (source port number).
The script is available here:
https://github.com/tohojo/netperf-wrapper/blob/master/misc/iperf-server.py
It should be pretty easy to make it listen to a socket instead and allow
clients to request 'their' data. If anyone thinks this will be useful,
I'll be happy to poke some more at it. :)
-Toke
--
Toke Høiland-Jørgensen
toke@toke.dk