Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(83) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(29) |
Feb
(43) |
Mar
(9) |
Apr
(9) |
May
(21) |
Jun
(43) |
Jul
(32) |
Aug
(12) |
Sep
(17) |
Oct
(29) |
Nov
(9) |
Dec
(15) |
| 2004 |
Jan
(8) |
Feb
(48) |
Mar
(50) |
Apr
(37) |
May
(12) |
Jun
(14) |
Jul
(33) |
Aug
(26) |
Sep
(16) |
Oct
(38) |
Nov
(39) |
Dec
(12) |
| 2005 |
Jan
(5) |
Feb
(22) |
Mar
(19) |
Apr
(24) |
May
(34) |
Jun
(21) |
Jul
(38) |
Aug
(14) |
Sep
(39) |
Oct
(25) |
Nov
(28) |
Dec
(18) |
| 2006 |
Jan
(19) |
Feb
(17) |
Mar
(47) |
Apr
(14) |
May
(27) |
Jun
(33) |
Jul
(3) |
Aug
(29) |
Sep
(12) |
Oct
(6) |
Nov
(8) |
Dec
(7) |
| 2007 |
Jan
(6) |
Feb
(11) |
Mar
(8) |
Apr
(7) |
May
(17) |
Jun
(24) |
Jul
(20) |
Aug
(25) |
Sep
(6) |
Oct
(7) |
Nov
(8) |
Dec
(5) |
| 2008 |
Jan
(7) |
Feb
(9) |
Mar
(22) |
Apr
(22) |
May
(33) |
Jun
(10) |
Jul
(15) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(5) |
| 2009 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(5) |
May
(4) |
Jun
(5) |
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
(7) |
Nov
(11) |
Dec
(12) |
| 2010 |
Jan
|
Feb
(16) |
Mar
(27) |
Apr
(40) |
May
(13) |
Jun
(11) |
Jul
(10) |
Aug
(8) |
Sep
(9) |
Oct
(2) |
Nov
(5) |
Dec
(6) |
| 2011 |
Jan
(9) |
Feb
|
Mar
(17) |
Apr
(15) |
May
(4) |
Jun
(10) |
Jul
(9) |
Aug
(4) |
Sep
(4) |
Oct
(11) |
Nov
(12) |
Dec
(4) |
| 2012 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(9) |
May
(6) |
Jun
|
Jul
(6) |
Aug
(6) |
Sep
(3) |
Oct
(1) |
Nov
(3) |
Dec
(8) |
| 2013 |
Jan
(2) |
Feb
(4) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(6) |
Aug
(2) |
Sep
(2) |
Oct
(10) |
Nov
(4) |
Dec
(3) |
| 2014 |
Jan
(3) |
Feb
(17) |
Mar
(5) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(5) |
Aug
(36) |
Sep
(51) |
Oct
(2) |
Nov
(8) |
Dec
(6) |
| 2015 |
Jan
(26) |
Feb
(3) |
Mar
(9) |
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(9) |
Mar
|
Apr
|
May
|
Jun
(13) |
Jul
(16) |
Aug
(8) |
Sep
(2) |
Oct
(11) |
Nov
(7) |
Dec
|
| 2017 |
Jan
(25) |
Feb
(8) |
Mar
(8) |
Apr
(3) |
May
(12) |
Jun
(18) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
(2) |
Feb
(8) |
Mar
(2) |
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
|
14
|
15
(1) |
16
|
17
|
18
(1) |
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
(1) |
27
|
|
28
(1) |
29
|
30
(1) |
|
|
|
|
|
From: Kok Leong Chia <kgaihc@ho...> - 2010-11-30 05:39:57
|
I am trying to perform iPERF test in dual mode (-d), but encountered the following problems. 1. Using: iperf -c 157.234.216.11 -u -i 1 -d Client side shows: ------------------------------------------------------------ Client connecting to 157.234.216.11, UDP port 5001 Sending 1470 byte datagrams UDP buffer size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 10.66.134.172 port 4220 connected with 157.234.216.11 port 5001 ------------------------------------------------------------ Server listening on UDP port 5001 Receiving 1470 byte datagrams UDP buffer size: 64.0 KByte (default) ------------------------------------------------------------ [ ID] Interval Transfer Bandwidth [ 4] 0.0- 1.0 sec 129 KBytes 1.06 Mbits/sec [ 4] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 2.0- 3.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 3.0- 4.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 4.0- 5.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 5.0- 6.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 6.0- 7.0 sec 129 KBytes 1.06 Mbits/sec [ 4] 7.0- 8.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 8.0- 9.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 9.0-10.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec [ 4] Sent 893 datagrams [ 4] WARNING: did not receive ack of last datagram after 10 tries. Problem: It only shows the uplink values, and iPERF hang and didn't return. 2. Using: iperf -c 157.234.216.11 -u -i 1 -d -B 10.66.134.172 Client side shows: bind failed: Address already in use ------------------------------------------------------------ Client connecting to 157.234.216.11, UDP port 5001 Binding to local address 10.66.134.172 Sending 1470 byte datagrams UDP buffer size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 10.66.134.172 port 4354 connected with 157.234.216.11 port 5001 ------------------------------------------------------------ Server listening on UDP port 5001 Binding to local address 10.66.134.172 Receiving 1470 byte datagrams UDP buffer size: 64.0 KByte (default) ------------------------------------------------------------ [ ID] Interval Transfer Bandwidth [ 4] 0.0- 1.0 sec 129 KBytes 1.06 Mbits/sec [ 4] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 2.0- 3.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 3.0- 4.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 4.0- 5.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 5.0- 6.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 6.0- 7.0 sec 129 KBytes 1.06 Mbits/sec [ 4] 7.0- 8.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 8.0- 9.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 9.0-10.0 sec 128 KBytes 1.05 Mbits/sec [ 4] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec [ 4] Sent 893 datagrams [ 4] WARNING: did not receive ack of last datagram after 10 tries. Problem: There is a "bind failed" error. It only shows the uplink values, and iPERF hangs and didn't return. Please help. Thanks. |
|
From: Usman S. Ansari <uansari@ya...> - 2010-11-28 18:43:32
|
Appreciate if someone can shed light on this.
I am running iperf on two systems connected via 10 GB cards. I am seeing lot of difference between through put reported by server and client.
Iperf threads Through put report Gb/s
(by server) / (by client)
3 8.68 / 8.68 <=== same ===
4 8.61 / 9.47 <=== different ===
In past I have seen differences in through put reported by server and client, but not by this much.
Can someone tell why this is so and which number to trust ?
Thanks
|
|
From: Siva Pothireddy <sivasanath@gm...> - 2010-11-26 06:53:17
|
Hi , Has anybody ported iperf for wince 6.0, i have seen some compilation steps for embedded vc++ 3.0, i tried that for quite some time, but it didnt work. can any body share the iperf application on wince, or please let me know how to compile, i am really in need of this, Thanks in Advance Siva |
|
From: Joseph Chiarelli <jchiarelli@ma...> - 2010-11-18 17:28:03
|
When I start a 2.0.5 client with the dual option (-d) sometime the server gets hung. ( and the client cant reconnect to the socket). I see this bug from 2.0.4 'iperf -s' exits when client connects with -d flag but not sure if this patch is in 2.0.5 or not. Any help is appreciated. |
|
From: martin <m4rtin86@gm...> - 2010-11-15 11:30:17
|
Me and a friend of mine troubleshooted one issue with TCP throughput and used "TCP window size flag" option of Iperf. The problem was, that Iperf often ignored this flag. For example like this: TCP window size: 16 KByte (WARNING: requested 150 KByte) However, I tested now between a FreeBSD, Ubuntu and Suse machine using Iperf versions 2.0.4 and 2.0.5 and now it seemed to be working. Have you encountered any issues with "TCP window size flag"? Should TCP window size be configured only at client side or server side as well? thanks you in advance! |