chyba to jednak komenda:
-d powoduje generowanie takich dziwnych informacji
sent 131072 bytes of 131072, pending 0, total 1128267776
sent 131072 bytes of 131072, pending 0, total 1128398848
sent 131072 bytes of 131072, pending 0, total 1128529920
sent 131072 bytes of 131072, pending 0, total 1128660992
sent 131072 bytes of 131072, pending 0, total 1128792064
sent 131072 bytes of 131072, pending 0, total 1128923136
sent 131072 bytes of 131072, pending 0, total 1129054208
sent 131072 bytes of 131072, pending 0, total 1129185280
sent 131072 bytes of 131072, pending 0, total 1129316352
sent 131072 bytes of 131072, pending 0, total 1129447424
sent 131072 bytes of 131072, pending 0, total 1129578496
sent 131072 bytes of 131072, pending 0, total 1129709568
i dopiero na końcu
Reading new State from the Server - current state is 13-EXCHANGE_RESULTS
State change: client received and changed State to 14-DISPLAY_RESULTS
interval_len 1.000215 bytes_transferred 117440512
interval forces keep
[ 5] 9.00-10.00 sec 112 MBytes 939 Mbits/sec 0 706 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.09 GBytes 938 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 1.09 GBytes 935 Mbits/sec receiver
State change: State set to 16-IPERF_DONE (from 14-DISPLAY_RESULTS)
Receiver threads stopped
Dla mnie najlepsze wyniki daje taka komenda
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-2.00 sec 111 MBytes 465 Mbits/sec 0 sender
[ 5] 0.00-2.00 sec 110 MBytes 459 Mbits/sec receiver
[ 7] 0.00-2.00 sec 223 MBytes 933 Mbits/sec 0 sender
[ 7] 0.00-2.00 sec 220 MBytes 922 Mbits/sec receiver
[ 9] 0.00-2.00 sec 112 MBytes 470 Mbits/sec 0 sender
[ 9] 0.00-2.00 sec 111 MBytes 463 Mbits/sec receiver
[SUM] 0.00-2.00 sec 446 MBytes 1.87 Gbits/sec 0 sender
[SUM] 0.00-2.00 sec 441 MBytes 1.84 Gbits/sec receiver