Re: Initial 2.0.a results
The CSV format follows the regular output in fields that follow the
datestamp, IP and port addresses. So for TCP or clientside UDP you get
socket number, timeframe, bytes transfered, bits/sec. For serverside UDP
or client reporting of server stats you get socket number, timeframe,
bytes transferred, bits/sec, jitter (ms), lost packets, total packets,
percent lost, out-of-order packets (this one is actually a second line of
output in the regular reporting style when the value is greater than 0).
As for the reporting of 7.4 seconds I am not sure what is up. When you ran
this tests what was the output from the 1.7 server? Did it report a
connection of ~7 seconds or did it show a full 10 secs? Also the Mbits
transferred on the regular reporting of server stats, is a bug and should
have been translated to MBytes, this is due to the format for server stats
not getting initialize correctly. It will be fixed.
Kevin
On Wed, 17 Dec 2003, Gregg Hamby wrote:
> Hello. This is just a summary of my initial results with the 2.0.a release today.
> I can say that the source configures and compiles just fine on my stock install of Red Hat 8. I am by no means a Linux whiz and getting the code to compile was no problem whatsoever.
>
> I've pasted two sets of results below. In both cases I simply ran the client and a UDP stream to an existing Iperf 1.7 server also running on Linux 8.
> For the second run I used the csv option and there appear to be a couple of fields that I can't figure out. The datestamp and IP addresses, port numbers, etc are obvious but can anyone describe the others?
> Also, every time I run it the server report comes back with an interval of 0.0-7.4 secs instead of the usual 0.0 - 10.0 as it does on 1.7
> Thanks.
>
> ------------------------------------------------------------
> Client connecting to 10.1.140.16, UDP port 5001
> Sending 1470 byte datagrams
> UDP buffer size: 64.0 KByte (default)
> ------------------------------------------------------------
> [ 5] local 10.1.100.117 port 32769 connected with 10.1.140.16 port 5001
> [ 5] 0.0- 1.0 sec 129 KBytes 1.06 Mbits/sec
> [ 5] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 2.0- 3.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 3.0- 4.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 4.0- 5.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 5.0- 6.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 6.0- 7.0 sec 129 KBytes 1.06 Mbits/sec
> [ 5] 7.0- 8.0 sec 126 KBytes 1.03 Mbits/sec
> [ 5] 8.0- 9.0 sec 129 KBytes 1.06 Mbits/sec
> [ 5] 9.0-10.0 sec 128 KBytes 1.05 Mbits/sec
> [ 5] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec
> [ 5] Sent 893 datagrams
> [ 5] Server Report:
> [ 5] 0.0- 7.3 sec 10.1 Mbits 1.38 Mbits/sec 3.929 ms 33/ 893 (3.7%)
> 20031217144839,10.1.100.117,32769,10.1.140.16,5001,5,0.0-1.0,132300,1058400
> 20031217144840,10.1.100.117,32769,10.1.140.16,5001,5,1.0-2.0,130830,1046640
> 20031217144841,10.1.100.117,32769,10.1.140.16,5001,5,2.0-3.0,130830,1046640
> 20031217144842,10.1.100.117,32769,10.1.140.16,5001,5,3.0-4.0,130830,1046640
> 20031217144843,10.1.100.117,32769,10.1.140.16,5001,5,4.0-5.0,130830,1046640
> 20031217144844,10.1.100.117,32769,10.1.140.16,5001,5,5.0-6.0,130830,1046640
> 20031217144845,10.1.100.117,32769,10.1.140.16,5001,5,6.0-7.0,132300,1058400
> 20031217144846,10.1.100.117,32769,10.1.140.16,5001,5,7.0-8.0,130830,1046640
> 20031217144847,10.1.100.117,32769,10.1.140.16,5001,5,8.0-9.0,130830,1046640
> 20031217144848,10.1.100.117,32769,10.1.140.16,5001,5,9.0-10.0,130830,1046640
> 20031217144848,10.1.100.117,32769,10.1.140.16,5001,5,0.0-10.0,1312710,1048561
> 20031217144848,10.1.140.16,5001,10.1.100.117,32769,5,0.0-7.3,1274490,1387801,2.848,26,893,2.912,0