Re: [Bloat] latency measurement tools?

["Eggert, Lars" <lars@netapp.com>]

Thanks, I'll check it out!

Lars

On Feb 14, 2013, at 0:56, Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> "Eggert, Lars" <lars-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org> writes:
> 
>> what are the preferred measurement tools for latency under load? Are
>> any publicly available or is everyone basically rolling their own?
> 
> Hi Lars
> 
> Usually, people employ netperf and/or iperf to load up a link, and then
> do some sort of latency measurement while the link is loaded (through
> netperf or just straight ping). I'm the author of a python wrapper that
> handles this in a reproducible way, and which also has a prototype of
> the Realtime Response Under Load (RRUL) test incorporated. The wrapper
> is available here:
> 
> https://github.com/tohojo/netperf-wrapper
> 
> (Or just install it through pip with `pip install netperf-wrapper`).
> 
> Also see this page for some example test plots:
> 
> http://www.bufferbloat.net/projects/codel/wiki/RRUL_Rogues_Gallery
> 
> And this one for some general advise on benchmarking (though that is
> mostly relevant at lower bandwidths):
> 
> http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel
> 
>> (I'm esp. interested in tools that can deal with 10 GbE and faster LAN
>> fabrics.)
> 
> The RRUL test prototype runs four simultaneous TCP streams in each
> direction which can generally load up pretty much any link on a modern
> Linux kernel (though I haven't tested it personally on high-speed
> networks due to lack of hardware).
> 
> Good luck with the benchmarking. :)
> 
> -Toke
> 
> -- 
> Toke Høiland-Jørgensen
> toke@toke.dk