search

DD1984 / sockperf

Automatically exported from code.google.com/p/sockperf
Other
1 stars 0 forks source link

Throughput summary consider should also consider TCP header, not only UDP header #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
(note, there are 2 problems: 1 - about msg-size recomendation, and 2 - about 
truput calculation)

The following message is incorrect for TCP.
vperf: NOTE: test was performed, using msg-size=12. For getting maximum 
throughput consider using --msg_size=1472
vperf: Summary: Message Rate is 456309 [msg/sec]
vperf: Summary: BandWidth is 17.407 MBps (139.254 Mbps)

please replace it with something like:
vperf: NOTE: test was performed, using msg-size=12. For getting maximum 
throughput consider using --msg_size=1472 (UDP), or --msg_size=??? (TCP)

Original issue reported on code.google.com by igor.ivanov@itseez.com on 4 Apr 2011 at 6:32

GoogleCodeExporter commented 9 years ago 
imported from: http://argus-bg.dnsalias.org/issues/691

Original comment by igor.ivanov@itseez.com on 4 Apr 2011 at 7:12

GoogleCodeExporter commented 9 years ago 
Avner,
What benefit do you see in this? 
Such information can be seen from standard output as
...
sockperf[CLIENT] send on:
[ 0] IP = 127.0.1.1       PORT = 12345 # TCP
...

Note:
Standard output shows info about mix conection too
...
sockperf[CLIENT] send on:
[ 0] IP = 127.0.1.1       PORT = 12345 # TCP
[ 1] IP = 127.0.1.1       PORT = 12346 # UDP
...

Original comment by igor.ivanov@itseez.com on 8 Apr 2011 at 1:43