Chapter 2. Monitoring and benchmark tools 75
Draft Document for Review May 4, 2007 11:35 am 4285ch02.fm
-l <testlen> Test length of benchmarking. If positive value is set, netperf perform
the benchmarking in testlen seconds. If negative, it performs until
value of testlen bytes data is exchanged for bulk data transfer
benchmarking or value of testlen transactions for request/response
type.
-c Local CPU utilization report
-C Remote CPU utilization report
-I <conflevel><interval>
This option is used to maintain confidence of the result. The
confidence level should be 99 or 95 (percent) and interval (percent)
can be set as well. To keep the result a certain level of confidence, the
netperf repeats the same benchmarking several times. For example,
-I 99,5 means that the result is within 5% interval (+- 2.5%) of the real
result in 99 times out of 100.
-i <max><min> Number of maximum and minimum test iterations. This option limits
the number of iteration. -i 10,3 means netperf perform same
benchmarking at least 3 times and at most 10 times. If the iteration
exceeds the maximum value, the result would not be in the confidence
level which is specified with -I option and some warning will be
displayed in the result.
-s <bytes>, -S <bytes>
Changes send and receive buffer size on local, remote system. This
will affect the advertised and effective window size.
Options for TCP_STREAM, TCP_MAERTS, TCP_SENDFILE, UDP_STREAM
-m <bytes>, -M <bytes>
Specifies the size of buffer passed to send(), recv() function call
respectively and control the size sent and received per call.
Options for TCP_RR, TCP_CC, TCP_CRR, UDP_RR:
-r <bytes>, -R <bytes>
Specifies request, response size respectively. For example, -r
128,8129 means that netperf send 128 byte packets to the netserver
and it sends the 8129 byte packets back to netperf.
The following is an example output of netperf for TCP_CRR type benchmark.
Example 2-27 An example result of TCP_CRR benchmark
Testing with the following command line:
/usr/local/bin/netperf -l 60 -H plnxsu4 -t TCP_CRR -c 100 -C 100 -i ,3 -I 95,5 -v
1 -- -r 64,1 -s 0 -S 512
TCP Connect/Request/Response TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to plnxsu4
(10.0.0.4) port 0 AF_INET
Local /Remote
Socket Size Request Resp. Elapsed Trans. CPU CPU S.dem S.dem
Send Recv Size Size Time Rate local remote local remote
bytes bytes bytes bytes secs. per sec % % us/Tr us/Tr
Note: The report of the CPU utilization may not be accurate in some platform. Make sure if
it is accurate before you perform benchmarking.