Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


iperf help
New on LowEndTalk? Please Register and read our Community Rules.

iperf help

Hi all, I am trying to understand what do these commands mean and how it can determine whether the network is really bad or good for my KS-LE box.

If someone can ELI5 what below commands mean and what should I look for in the OP to determine whether there is something at fault or not. Currently the server is in rescue mode...

Overall I feel my KS-LE (BHS) is not performing as expected.

Thanks!

1. iperf -c iperf.ovh.net -i 1

------------------------------------------------------------
Client connecting to iperf.ovh.net, TCP port 5001
TCP window size: 45.0 KByte (default)
------------------------------------------------------------
[  3] local 158.69.252.XXX port 51656 connected with 188.165.12.136 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3]  1.0- 2.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3]  2.0- 3.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3]  3.0- 4.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3]  4.0- 5.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  5.0- 6.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  6.0- 7.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3]  7.0- 8.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3]  8.0- 9.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3]  9.0-10.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3]  0.0-10.0 sec  17.6 MBytes  14.8 Mbits/sec

2. iperf -c iperf.ovh.net -i 1 -u -b 1g

------------------------------------------------------------
Client connecting to iperf.ovh.net, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 158.69.252.XXX port 58280 connected with 188.165.12.136 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  1.0- 2.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  2.0- 3.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  3.0- 4.0 sec  97.1 MBytes   814 Mbits/sec
[  3]  4.0- 5.0 sec  96.9 MBytes   813 Mbits/sec
[  3]  5.0- 6.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  6.0- 7.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  7.0- 8.0 sec  97.1 MBytes   815 Mbits/sec
[  3]  8.0- 9.0 sec  97.0 MBytes   814 Mbits/sec
[  3]  9.0-10.0 sec  97.0 MBytes   814 Mbits/sec
[  3]  0.0-10.0 sec   971 MBytes   814 Mbits/sec
[  3] Sent 692500 datagrams
read failed: Connection refused
[  3] WARNING: did not receive ack of last datagram after 1 tries.

3. iperf -c iperf.ovh.net -m -i 1 -t 10 -r

------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  128 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to iperf.ovh.net, TCP port 5001
TCP window size: 45.0 KByte (default)
------------------------------------------------------------
[  5] local 158.69.252.XXX port 51658 connected with 188.165.12.136 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0- 1.0 sec  1.62 MBytes  13.6 Mbits/sec
[  5]  1.0- 2.0 sec  1.50 MBytes  12.6 Mbits/sec
[  5]  2.0- 3.0 sec  1.50 MBytes  12.6 Mbits/sec
[  5]  3.0- 4.0 sec  1.62 MBytes  13.6 Mbits/sec
[  5]  4.0- 5.0 sec  1.75 MBytes  14.7 Mbits/sec
[  5]  5.0- 6.0 sec  2.00 MBytes  16.8 Mbits/sec
[  5]  6.0- 7.0 sec  2.00 MBytes  16.8 Mbits/sec
[  5]  7.0- 8.0 sec  2.00 MBytes  16.8 Mbits/sec
[  5]  8.0- 9.0 sec  2.25 MBytes  18.9 Mbits/sec
[  5]  9.0-10.0 sec  2.50 MBytes  21.0 Mbits/sec
[  5]  0.0-10.0 sec  18.9 MBytes  15.8 Mbits/sec
[  5] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
[  4] local 158.69.252.XXX port 5001 connected with 188.165.12.136 port 48887
[  4]  0.0- 1.0 sec  14.7 MBytes   124 Mbits/sec
[  4]  1.0- 2.0 sec  33.0 MBytes   277 Mbits/sec
[  4]  2.0- 3.0 sec  32.2 MBytes   270 Mbits/sec
[  4]  3.0- 4.0 sec  31.0 MBytes   260 Mbits/sec
[  4]  4.0- 5.0 sec  33.0 MBytes   277 Mbits/sec
[  4]  5.0- 6.0 sec  33.0 MBytes   277 Mbits/sec
[  4]  6.0- 7.0 sec  30.8 MBytes   258 Mbits/sec
[  4]  7.0- 8.0 sec  32.5 MBytes   272 Mbits/sec
[  4]  8.0- 9.0 sec  33.0 MBytes   277 Mbits/sec
[  4]  9.0-10.0 sec  31.8 MBytes   266 Mbits/sec
[  4]  0.0-10.0 sec   306 MBytes   257 Mbits/sec
[  4] MSS size 1448 bytes (MTU 1500 bytes, ethernet)

yabs.sh -

[email protected]:~# curl -sL yabs.sh | bash -s -- -fg
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2021-12-03                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Wed Dec  8 13:03:27 EST 2021

Basic System Information:
---------------------------------
Processor  : Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz
CPU cores  : 8 @ 1295.905 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 31.3 GiB
Swap       : 0.0 KiB
Disk       :

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed
                |                           |                 |
Clouvider       | London, UK (10G)          | 33.6 Mbits/sec  | 172 Mbits/sec
Online.net      | Paris, FR (10G)           | 32.8 Mbits/sec  | 172 Mbits/sec
WorldStream     | The Netherlands (10G)     | 36.8 Mbits/sec  | 145 Mbits/sec
WebHorizon      | Singapore (1G)            | 11.4 Mbits/sec  | busy
Clouvider       | NYC, NY, US (10G)         | 95.3 Mbits/sec  | 363 Mbits/sec
Velocity Online | Tallahassee, FL, US (10G) | 62.0 Mbits/sec  | 180 Mbits/sec
Clouvider       | Los Angeles, CA, US (10G) | 49.3 Mbits/sec  | 88.2 Mbits/sec
Iveloz Telecom  | Sao Paulo, BR (2G)        | 18.1 Mbits/sec  | 92.5 Mbits/sec

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed
                |                           |                 |
Clouvider       | London, UK (10G)          | 35.0 Mbits/sec  | 152 Mbits/sec
Online.net      | Paris, FR (10G)           | 35.0 Mbits/sec  | 118 Mbits/sec
WorldStream     | The Netherlands (10G)     | 33.0 Mbits/sec  | 166 Mbits/sec
WebHorizon      | Singapore (1G)            | 16.9 Mbits/sec  | 101 Mbits/sec
Clouvider       | NYC, NY, US (10G)         | 93.8 Mbits/sec  | 360 Mbits/sec
Clouvider       | Los Angeles, CA, US (10G) | 47.3 Mbits/sec  | 108 Mbits/sec

Comments

  • Poor outgoing connection..

    Thanked by 2plumberg skorous
  • You have a very low TCP number compared to UDP. This implies you have a fat pipe, but you have latency or packet loss. Since the throughout is steady, it is not likely to be packet loss.

    What is the ping time?

    What TCP throughput don't you get if you add "-P 3” to the commands without -b? This should get you the peak TCP throughput achievable.

    Have you enabled bbr?

  • @TimboJones said:
    You have a very low TCP number compared to UDP. This implies you have a fat pipe, but you have latency or packet loss. Since the throughout is steady, it is not likely to be packet loss.

    What is the ping time?

    What TCP throughput don't you get if you add "-P 3” to the commands without -b? This should get you the peak TCP throughput achievable.

    Have you enabled bbr?

    What's bbr? It's on rescue mode so it should have any and all optimal settings I think

    I'll add the other -P flag and share findings...

  • @plumberg said:

    @TimboJones said:
    You have a very low TCP number compared to UDP. This implies you have a fat pipe, but you have latency or packet loss. Since the throughout is steady, it is not likely to be packet loss.

    What is the ping time?

    What TCP throughput don't you get if you add "-P 3” to the commands without -b? This should get you the peak TCP throughput achievable.

    Have you enabled bbr?

    What's bbr? It's on rescue mode so it should have any and all optimal settings I think

    I'll add the other -P flag and share findings...

    I doubt running in rescue mode works the same as normal boot. Full initialization, buffers, counters, timers, etc. /shrug

    BBR is another TCP algorithm that Google designed to work better over longer distances and packet loss. Typically, it results in huge improvement over default.

    Google "enable bbr on $your_os".

    Thanked by 1plumberg
Sign In or Register to comment.