Re: netperf

On 01/28/2014 01:49 PM, Анна Будкина wrote:

2014-01-28 Sebastian Sumpf <Sebastian.Sumpf@...1... mailto:Sebastian.Sumpf@...1...>

On 01/28/2014 01:20 PM, Christian Helmuth wrote:
> Sebastian,
>
> On Tue, Jan 28, 2014 at 01:07:19PM +0100, Sebastian Sumpf wrote:
>> Thanks for your tests! But I don't like the 65 MBit/s thing! What is
>> going on? Is this RX or TX?
>
> Complete netperf output follows
>
> ---------------------------- TCP_STREAM -----------------------
> spawn netperf-2.6.0 -H 10.0.0.65 -P 1 -v 2 -t TCP_STREAM -c -C --
-m 1024
> MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
10.0.0.65 () port 0 AF_INET
> 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      % U    
 us/KB   us/KB
>
>  87380  16384   1024    10.02        65.59   34.95    -1.00  
 174.598  -1.249
>
> Alignment      Offset         Bytes    Bytes       Sends   Bytes  
 Recvs
> Local  Remote  Local  Remote  Xfered   Per                 Per
> Send   Recv    Send   Recv             Send (avg)          Recv (avg)
>     8       8      0       0 82158592  1024.00     80233   8905.12
  9226
>
> Maximum
> Segment
> Size (bytes)
>   1448
>
> calculation: overall bytes / size per packet / time = packets per
second
>              82158592 Bytes / 1024 Bytes / 10.02 s =     8007
packets/s
>
> ! PERF: TCP_STREAM              65.59 MBit/s ok
>
> ---------------------------- TCP_MAERTS -----------------------
> spawn netperf-2.6.0 -H 10.0.0.65 -P 1 -v 2 -t TCP_MAERTS -c -C --
-m 1024
> MIGRATED TCP MAERTS TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
10.0.0.65 () port 0 AF_INET
> Recv   Send    Send                          Utilization      
Service Demand
> Socket Socket  Message  Elapsed              Recv     Send    
Recv    Send
> Size   Size    Size     Time     Throughput  local    remote  
local   remote
> bytes  bytes   bytes    secs.    10^6bits/s  % S      % U    
 us/KB   us/KB
>
>  87380  16384   1024    10.00       543.35   39.06    -1.00  
 23.555  -0.151
>
> Alignment      Offset         Bytes    Bytes       Recvs   Bytes  
 Sends
> Local  Remote  Local  Remote  Xfered   Per                 Per
> Recv   Send    Recv   Send             Recv (avg)          Send (avg)
>     8       8      0       0 679280808  13875.90     48954  
16384.00  41474
>
> Maximum
> Segment
> Size (bytes)
>   1448
>
> calculation: overall bytes / size per packet / time = packets per
second
>              679280808 Bytes / 1024 Bytes / 10.00 s =    66336
packets/s
>
> ! PERF: TCP_MAERTS              543.35 MBit/s ok
>
>
> The manual states
>
>   TCP_STREAM  It is quite simple, transferring some quantity of data
>               from the system running netperf to the system running
>               netserver.
>   TCP_MAERTS  A TCP_MAERTS (MAERTS is STREAM backwards) test is “just
>               like” a TCP_STREAM test except the data flows from the
>               netserver to the netperf.
>
> So, the scenario is much slower if the Genode side is _receiving_.

Without cursing: This is no good! I will look into that!

Thank you very much for the reply! I will try to use Genode on Nova to perform these tests.

So, it is x86 i guess.

Sebastian