[netperf-talk] Testing on Freescale MPC8313ERDB

Andrew Gallatin gallatin at cs.duke.edu
Wed May 5 13:08:48 PDT 2010


Rick Jones wrote:
> Dominic Lemire wrote:

> and make certain your CPU is not saturated.  If there is any question 
> whatsoever the remote CPU might be bottlenecking, you should check there 
> too - add a "-C" after the "-c"

And if the CPU is saturated on the sender, try using the sendfile
test:

./netperf -H 192.168.1.1 -c -C -tTCP_SENDFILE -F /path/to/a/big/file

This eliminates the copy on the transmit side.

Are there multiple CPUS (cores?) on this system, if yes
and your CPU is still saturated, then try using the -T CPU binding
options and multiple copies of netperf.  Assuming 2 quad-cores

netperf -H 192.168.1.1 -T0,0 -P 0 -l 120 &
netperf -H 192.168.1.1 -T1,1 -P 0 -l 120 &
netperf -H 192.168.1.1 -T2,2 -P 0 -l 120 &
netperf -H 192.168.1.1 -T3,3 -P 0 -l 120 &

Note the "-l 120", which is intended to run a longer
test, and minimize the percent of time when not all
4 are running at once.   To really do a multithreaded
test, you need netperf4, uperf, or even iperf.

Drew


More information about the netperf-talk mailing list