[netperf-talk] global question concerning Netperf test and SMP support
Simon Duboue
Simon.Duboue at ces.ch
Mon Apr 30 09:30:08 PDT 2012
>> Ok, this is a good complementary check. Here is the result of the first
>> test I do concerning service demand:
>> single test:
>> netperf -l 60 -H 10.0.17.200 -i 10,2 -I 99,5 -t TCP_STREAM -cC
>> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.0.17.200
>> (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
>> Recv Send Send Utilization Service Demand
>> Socket Socket Message Elapsed Send Recv Send Recv
>> Size Size Size Time Throughput local remote local remote
>> bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB
>>
>> 87380 65536 65536 60.01 2075.12 *5.19 9.32 0.409 3.027 *
>>
>>
>> two-at-once test:
>> netperf -l 60 -H 10.0.17.200 -i 10,2 -I 99,5 -t TCP_STREAM -cC &
>> netperf -l 60 -H 10.0.17.200 -i 10,2 -I 99,5 -t TCP_STREAM -cC
>>
>> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.0.17.200
>> (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
>> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.0.17.200
>> (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
>>
>> Recv Send Send Utilization Service Demand
>> Socket Socket Message Elapsed Send Recv Send Recv
>> Size Size Size Time Throughput local remote local remote
>> bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB
>>
>> 87380 65536 65536 60.06 1760.01 *9.21 13.11 0.858 4.801 *
>>
>> Recv Send Send Utilization Service Demand
>> Socket Socket Message Elapsed Send Recv Send Recv
>> Size Size Size Time Throughput local remote local remote
>> bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB
>>
>> 87380 65536 65536 60.06 1750.31 *9.21 13.14 0.861 4.730*
>>
>> This looks good isn't it?
>
>That definitely looks better. However, you need to change the "-i 10,2"
>to "-i 10" You must not let netperf finish "early" if it hits the
>confidence interval, so the min and max iterations must be the same.
>
>rick
Ok, now I understand!
It seems more complicated for observing synchronization with UDP stream
test. Here is an example of what I try:
netperf -l 60 -H 10.0.17.200 -t UDP_STREAM -cC -i 10 -I 99,5 -- -m 8900 &
netperf -l 60 -H 10.0.17.200 -t UDP_STREAM -cC -i 10 -I 99,5 -- -m 8900 &
netperf -l 60 -H 10.0.17.200 -t UDP_STREAM -cC -i 10 -I 99,5 -- -m 8900
UDP UNIDIRECTIONAL SEND TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
10.0.17.200 (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
!!! WARNING
!!! Desired confidence was not achieved within the specified iterations.
!!! This implies that there was variability in the test environment that
!!! must be investigated before going further.
!!! Confidence intervals: Throughput : 2.3%
!!! Local CPU util : 1.9%
!!! Remote CPU util : 46.7%
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SS us/KB
112640 8900 60.00 2766708 0 3283.2 64.21 3.411
108544 60.00 2599612 3084.9 64.83 13.768
UDP UNIDIRECTIONAL SEND TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
10.0.17.200 (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
!!! WARNING
!!! Desired confidence was not achieved within the specified iterations.
!!! This implies that there was variability in the test environment that
!!! must be investigated before going further.
!!! Confidence intervals: Throughput : 1.9%
!!! Local CPU util : 1.8%
!!! Remote CPU util : 53.1%
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SS us/KB
112640 8900 60.00 2809476 0 3333.9 64.24 3.384
108544 60.00 2620965 3110.2 60.55 12.770
UDP UNIDIRECTIONAL SEND TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
10.0.17.200 (10.0.17.200) port 0 AF_INET : +/-2.5% @ 99% conf. : demo
!!! WARNING
!!! Desired confidence was not achieved within the specified iterations.
!!! This implies that there was variability in the test environment that
!!! must be investigated before going further.
!!! Confidence intervals: Throughput : 1.9%
!!! Local CPU util : 1.8%
!!! Remote CPU util : 48.5%
Socket Message Elapsed Messages CPU Service
Size Size Time Okay Errors Throughput Util Demand
bytes bytes secs # # 10^6bits/sec % SS us/KB
112640 8900 60.00 2790054 0 3310.9 64.23 3.399
108544 60.00 2609576 3096.7 59.35 12.560
Due to the protocol, the CPU utilization varies a lot. Could I only check
the local CPU utilization in order to make sure that tests are running
simultaneously? Do I need both to be near to consider UDP test as
synchronized? I also consider the service demand which is clearly higher
than with a single instance test.
I plan to try TCP sendfile also to compare results with TCP. Does the size
of the sent file matter?
A not related question: I try to use the -n option to choose the number of
core used by my remote computer but this seems not to be considered.
Does Netperf/Netserver consider this options or does it ignores it if it
can determine itself the number of cpu?
So, I will use CPU bind in order to do it manually.
Thank you and have a nice day.
Simon Duboué
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.netperf.org/pipermail/netperf-talk/attachments/20120430/9adec62f/attachment-0001.html>
More information about the netperf-talk
mailing list