On 5/11/11 7:54 PM, Tom Eastep wrote: > On 5/11/11 7:39 PM, Mr Dash Four wrote: >> >>> The calculations make sense. I think my first attempt to test this would >>> be to run parallel netperfs (one netperf per class) and look at the >>> output of 'shorewall show tc'. That will show you what the actual speeds >>> are. I don't recall if netperf provides any latency data. >>> >> Well, I did quite a bit of testing in the past couple of hours, but I >> am, quite frankly, unimpressed! >> >> I used netperf's biggest brother - iperf - instead. > > I consider iperf to be netperf's little sister
I recommended netperf because I already knew that iperf only reports throughput and not latency. When you vary TC parameters that only affect latency, you can't expect throughput to change. I still don't know if netperf reports latency information. I expected you to try it and let us know. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
