[netperf-talk] Problem with different runtime over wireless link

[Kai Koehne]

Hi,

I am having a hard time evaluating the performance of wireless links 
using netperf-2.4.3. I want to measure two wireless links which might 
interfere, and therefore started netperf in parallel on two different hosts:

host1$ netperf -H 192.168.3.121 -c -C -i 30 -t UDP_STREAM -l 10 -v 2 -d 
-d -- -H 192.168.100.121 -m 1472 -s 32768 -S 32768
host2$ netperf -H 192.168.3.120 -c -C -i 30 -t UDP_STREAM -l 10 -v 2 -d 
-d -- -H 192.168.101.120 -m 1472 -s 32768 -S 32768

To my understanding, the options say that 30 tests each one lasting 10 
seconds tests are run over the 192.168.100.* / 192.168.101.* networks 
(the wireless network), while the control channel is set up over the 
192.168.3.* networks (Ethernet).

In theory, netperf should run 10*30=300 seconds + some small overhead. 
However, one netperf instance in fact runs for 873 seconds, and the 
other one even for 2441 seconds! This of course invalids all results. I 
imagine this is due to a lot of packet losses.

Is there a way to ensure that netperf only runs for a specified amount 
of time? And if not, how will netperf4 handle such cases?

Kind regards,

Kai Köhne


PS: The detailed logs of both netperf runs (determined by -d -d) look 
quite similar. I did not attach them due to their size; however, if of 
interest I would happily send them to you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: koehne.vcf
Type: text/x-vcard
Size: 380 bytes
Desc: not available
Url : http://www.netperf.org/pipermail/netperf-talk/attachments/20070814/509e0cf2/attachment.vcf