I've just upgraded to the 18.06 branch and am seeing something a little strange, wonder if others have as well.
iperf3 test can't get over 60Mbps per stream. If i do a single threaded test, it's 60Mbps, on 4.9 kernel I could max out my connection easily with 6 parallel streams, now it takes at least 10.
Anything that could explain this?
I vaguely recall having a lan speed problem many months ago right after upgrading the firmware through LuCi. I think I solved the problem by using TFTP to re-flash the firmware.
Yep, this was via TFTP as I was coming from a 4.9 branch to 4.14 which needs the larger kernel partition. Guess I'll try a few more things.
OK, definitely an issue here - just updated to the latest commit of the 18.06, stripped out most of @hnyman 's patches (LED etc.) and I'm still seeing single iperf3 streams limited to around 60Mbps with flow offload on or off - SQM is disabled.
root@router01:/etc/init.d# iperf3 -c ping.online.net -p 5206 -R -Z
Connecting to host ping.online.net, port 5206
Reverse mode, remote host ping.online.net is sending
[ 5] local xxx.xxx.xxx.xxx port 38816 connected to 62.210.18.40 port 5206
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 5.01 MBytes 42.0 Mbits/sec
[ 5] 1.00-2.00 sec 7.61 MBytes 63.8 Mbits/sec
[ 5] 2.00-3.00 sec 7.35 MBytes 61.6 Mbits/sec
[ 5] 3.00-4.00 sec 7.62 MBytes 63.9 Mbits/sec
[ 5] 4.00-5.00 sec 7.63 MBytes 64.0 Mbits/sec
[ 5] 5.00-6.00 sec 7.66 MBytes 64.3 Mbits/sec
[ 5] 6.00-7.00 sec 7.59 MBytes 63.7 Mbits/sec
[ 5] 7.00-8.00 sec 7.67 MBytes 64.3 Mbits/sec
[ 5] 8.00-9.00 sec 7.46 MBytes 62.6 Mbits/sec
[ 5] 9.00-10.00 sec 7.63 MBytes 64.0 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 73.8 MBytes 61.9 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 73.2 MBytes 61.4 Mbits/sec receiver
iperf Done.
Anyone seen similar? For reference the stock firmware and previous master builds I was running got 380Mbps, which is near the limit of the connection (384Mbps)
@philjohn
Here are the results I get when IPERFing your server over a slow 4G connection:
root@R7800RT1:~# iperf3 -c 62.210.18.40 -p 5206 -R -Z
Connecting to host 62.210.18.40, port 5206
Reverse mode, remote host 62.210.18.40 is sending
[ 5] local xxx.xxx.xxx.xxx port 41186 connected to 62.210.18.40 port 5206
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 273 KBytes 2.23 Mbits/sec
[ 5] 1.00-2.00 sec 363 KBytes 2.97 Mbits/sec
[ 5] 2.00-3.00 sec 384 KBytes 3.15 Mbits/sec
[ 5] 3.00-4.00 sec 633 KBytes 5.18 Mbits/sec
[ 5] 4.00-5.00 sec 597 KBytes 4.89 Mbits/sec
[ 5] 5.00-6.00 sec 627 KBytes 5.14 Mbits/sec
[ 5] 6.00-7.00 sec 439 KBytes 3.59 Mbits/sec
[ 5] 7.00-8.00 sec 535 KBytes 4.39 Mbits/sec
[ 5] 8.00-9.00 sec 575 KBytes 4.71 Mbits/sec
[ 5] 9.00-10.00 sec 714 KBytes 5.85 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 5.53 MBytes 4.64 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 5.02 MBytes 4.21 Mbits/sec receiver
iperf Done.
If you downgrade the router firmware, does the performance increase back to 380Mbps or does it stay at 60Mbps?
ATM, I can't think of anything else to try.
Here are my iperf3 results connecting to the same server (only on a different port) through my 500/500 ISP link:
iperf3 -c ping.online.net -p 5205 -R -Z
Connecting to host ping.online.net, port 5205
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 53408 connected to 62.210.18.40 port 5205
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 3.16 MBytes 26.5 Mbits/sec
[ 5] 1.00-2.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 2.00-3.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 3.00-4.00 sec 4.74 MBytes 39.8 Mbits/sec
[ 5] 4.00-5.00 sec 4.69 MBytes 39.3 Mbits/sec
[ 5] 5.00-6.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 6.00-7.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 7.00-8.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 8.00-9.00 sec 4.64 MBytes 38.9 Mbits/sec
[ 5] 9.00-10.00 sec 4.78 MBytes 40.1 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 45.7 MBytes 38.3 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 45.2 MBytes 37.9 Mbits/sec receiver
I did this on r7275-512c57e7f3 which I TFTP flashed. My build is based on the master tree with some additional packages included, but I did my test without restoring my configuration backup (i.e no SQM or anything else running that might otherwise impact the result).
I also re-ran the test to check whether connecting to port 5206 produced a different result, but it's the same.
Yep, there's definitely a performanc eregression here then - ping.online.net is on a 10Gb connection and should be able to max out a 500/500 connection during a test.
@Magnetron1.1 I reverted to stock and a LEDE 17.01 build, both were giving me full speed, as was my previous master build which was r6739-5950ab067b which is what I'm about to revert back to to test again.
hnyman
June 20, 2018, 6:08am
1218
Would be great if somebody (with a speedy connection) can find the regression point in either master and/or 18.06. That might require building/testing a few versions from the past weeks.
Yep, I'm on it. My connection is 384/20.
I'm going back to my previous master build now to start as a reference point and then I'll try the version just before 4.14, once 4.14 was enabled and work from there.
1 Like
Ansuel
June 20, 2018, 7:46am
1220
Flow offload patch could be the culprit?
Could be - although I'm getting the same result with flow offload enabled and disabled, so you would hope in the disabled state it's not actually running that code ... but I suppose we'll find out later, about to flash my "last known good" master build and will then work from there.
Update 2: revision 7007 flashes and works, but I can't SSH in to run iperf3
Update: revision 6985 (last before 4.14 changes and kernel partition resize) also sees full performance.
OK, revision 6739 gets full beans:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5207 -R
Connecting to host ping.online.net, port 5207
Reverse mode, remote host ping.online.net is sending
[ 5] local xxx.xxx.xxx.xxx port 46784 connected to 62.210.18.40 port 5207
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 6.71 MBytes 56.3 Mbits/sec
[ 5] 1.00-2.00 sec 18.8 MBytes 157 Mbits/sec
[ 5] 2.00-3.00 sec 23.5 MBytes 197 Mbits/sec
[ 5] 3.00-4.00 sec 32.8 MBytes 275 Mbits/sec
[ 5] 4.00-5.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 5.00-6.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 6.00-7.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 7.00-8.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 8.00-9.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 9.00-10.00 sec 45.8 MBytes 384 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 361 MBytes 303 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 356 MBytes 299 Mbits/sec receiver
Going to try a master just before the 4.14 for ipq806x went in to see if that is still fast, then first stable build of 4.14 (after the flurry of commits)
I get the same results with r6985:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5205 -R
Connecting to host ping.online.net, port 5205
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 58508 connected to 62.210.18.40 port 5205
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 3.34 MBytes 28.0 Mbits/sec
[ 5] 1.00-2.00 sec 8.44 MBytes 70.7 Mbits/sec
[ 5] 2.00-3.00 sec 18.1 MBytes 152 Mbits/sec
[ 5] 3.00-4.00 sec 42.7 MBytes 358 Mbits/sec
[ 5] 4.00-5.00 sec 45.5 MBytes 382 Mbits/sec
[ 5] 5.00-6.00 sec 45.9 MBytes 385 Mbits/sec
[ 5] 6.00-7.00 sec 45.5 MBytes 381 Mbits/sec
[ 5] 7.00-8.00 sec 45.9 MBytes 385 Mbits/sec
[ 5] 8.00-9.00 sec 45.6 MBytes 383 Mbits/sec
[ 5] 9.00-10.00 sec 45.9 MBytes 385 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 351 MBytes 294 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 347 MBytes 291 Mbits/sec receiver
iperf Done.
Seems like a single stream caps out at ~385 Mbit/sec at this revision. I'm able to max out my connection with two parallel streams:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5205 -R -P 2
Connecting to host ping.online.net, port 5205
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 58526 connected to 62.210.18.40 port 5205
[ 7] local 51.175.71.139 port 58528 connected to 62.210.18.40 port 5205
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 3.39 MBytes 28.5 Mbits/sec
[ 7] 0.00-1.00 sec 4.09 MBytes 34.3 Mbits/sec
[SUM] 0.00-1.00 sec 7.48 MBytes 62.8 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 1.00-2.00 sec 16.9 MBytes 142 Mbits/sec
[ 7] 1.00-2.00 sec 16.0 MBytes 134 Mbits/sec
[SUM] 1.00-2.00 sec 32.9 MBytes 276 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 2.00-3.00 sec 32.5 MBytes 273 Mbits/sec
[ 7] 2.00-3.00 sec 32.7 MBytes 275 Mbits/sec
[SUM] 2.00-3.00 sec 65.2 MBytes 548 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 3.00-4.00 sec 30.0 MBytes 252 Mbits/sec
[ 7] 3.00-4.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 3.00-4.00 sec 59.9 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 4.00-5.00 sec 30.1 MBytes 253 Mbits/sec
[ 7] 4.00-5.00 sec 29.9 MBytes 250 Mbits/sec
[SUM] 4.00-5.00 sec 60.0 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 5.00-6.00 sec 30.0 MBytes 252 Mbits/sec
[ 7] 5.00-6.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 5.00-6.00 sec 59.9 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 6.00-7.00 sec 30.1 MBytes 252 Mbits/sec
[ 7] 6.00-7.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 6.00-7.00 sec 59.9 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 7.00-8.00 sec 30.1 MBytes 252 Mbits/sec
[ 7] 7.00-8.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 7.00-8.00 sec 59.9 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 8.00-9.00 sec 30.0 MBytes 252 Mbits/sec
[ 7] 8.00-9.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 8.00-9.00 sec 59.9 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 9.00-10.00 sec 30.1 MBytes 252 Mbits/sec
[ 7] 9.00-10.00 sec 29.9 MBytes 251 Mbits/sec
[SUM] 9.00-10.00 sec 60.0 MBytes 503 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 267 MBytes 224 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 263 MBytes 221 Mbits/sec receiver
[ 7] 0.00-10.00 sec 267 MBytes 224 Mbits/sec 0 sender
[ 7] 0.00-10.00 sec 262 MBytes 220 Mbits/sec receiver
[SUM] 0.00-10.00 sec 534 MBytes 448 Mbits/sec 0 sender
[SUM] 0.00-10.00 sec 525 MBytes 441 Mbits/sec receiver
iperf Done.
Yep, that's to be expected. If you want to go faster with a single stream you could try the SFE patch that dissent1 put up on the old lede repo, that's the old hacky alternative to the nf flow offload that's in 4.14
So it points to there being something between 6985 and now that causes a huge drop in single stream performance.
Sadly I'm logged into work and running a pg_dump on a huge table that I don't want to interrupt, so can't go to the next version I have built, 7007, until that's finished sometime in the next hour or so.
1 Like
On the R7800 running r7184, with flow offloading enabled:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5205 -R
Connecting to host ping.online.net, port 5205
Reverse mode, remote host ping.online.net is sending
[ 5] local xxx.xxx.xxx.xxx port 49666 connected to 62.210.18.40 port 5205
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 15.8 MBytes 132 Mbits/sec
[ 5] 1.00-2.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 2.00-3.00 sec 16.6 MBytes 140 Mbits/sec
[ 5] 3.00-4.00 sec 16.6 MBytes 139 Mbits/sec
[ 5] 4.00-5.00 sec 16.8 MBytes 140 Mbits/sec
[ 5] 5.00-6.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 6.00-7.00 sec 16.6 MBytes 140 Mbits/sec
[ 5] 7.00-8.00 sec 16.8 MBytes 141 Mbits/sec
[ 5] 8.00-9.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 9.00-10.00 sec 16.7 MBytes 140 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 167 MBytes 140 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 166 MBytes 139 Mbits/sec receiver
iperf Done.
But on a Ubuntu machine connected to the R7800 by Ethernet:
$ iperf3 -c ping.online.net -p 5205 -R
Connecting to host ping.online.net, port 5205
Reverse mode, remote host ping.online.net is sending
[ 4] local 192.168.1.223 port 51042 connected to 62.210.18.40 port 5205
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 50.1 MBytes 420 Mbits/sec
[ 4] 1.00-2.00 sec 68.9 MBytes 578 Mbits/sec
[ 4] 2.00-3.00 sec 68.6 MBytes 576 Mbits/sec
[ 4] 3.00-4.00 sec 83.1 MBytes 697 Mbits/sec
[ 4] 4.00-5.00 sec 77.6 MBytes 651 Mbits/sec
[ 4] 5.00-6.00 sec 76.7 MBytes 643 Mbits/sec
[ 4] 6.00-7.00 sec 74.4 MBytes 624 Mbits/sec
[ 4] 7.00-8.00 sec 62.0 MBytes 520 Mbits/sec
[ 4] 8.00-9.00 sec 61.8 MBytes 519 Mbits/sec
[ 4] 9.00-10.00 sec 50.2 MBytes 421 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 680 MBytes 571 Mbits/sec 616 sender
[ 4] 0.00-10.00 sec 674 MBytes 565 Mbits/sec receiver
iperf Done.
I ran git bisect to identify the commit that causes the regression and I identified this kernel bump as the cause (r7106):
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=e52f3e9b13763cbfbd92fca8db0b4d19dc1e309e
I've run an iperf3 test on the preceding commit (r7105) to make sure the speeds are normal:
Link to commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=7590c3c58f5e9d580c86da10473d1d29a2f081c9
root@OpenWrt:~# iperf3 -c ping.online.net -p 5207 -R
Connecting to host ping.online.net, port 5207
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 48514 connected to 62.210.18.40 port 5207
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 2.24 MBytes 18.8 Mbits/sec
[ 5] 1.00-2.00 sec 17.1 MBytes 144 Mbits/sec
[ 5] 2.00-3.00 sec 35.6 MBytes 299 Mbits/sec
[ 5] 3.00-4.00 sec 39.4 MBytes 330 Mbits/sec
[ 5] 4.00-5.00 sec 39.3 MBytes 330 Mbits/sec
[ 5] 5.00-6.00 sec 39.1 MBytes 327 Mbits/sec
[ 5] 6.00-7.00 sec 38.7 MBytes 325 Mbits/sec
[ 5] 7.00-8.00 sec 39.1 MBytes 328 Mbits/sec
[ 5] 8.00-9.00 sec 39.3 MBytes 330 Mbits/sec
[ 5] 9.00-10.00 sec 38.8 MBytes 325 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 333 MBytes 280 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 329 MBytes 276 Mbits/sec receiver
Here are the speeds on the kernel bump commit:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5207 -R
Connecting to host ping.online.net, port 5207
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 45862 connected to 62.210.18.40 port 5207
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 2.42 MBytes 20.2 Mbits/sec
[ 5] 1.00-2.00 sec 3.44 MBytes 28.9 Mbits/sec
[ 5] 2.00-3.00 sec 3.61 MBytes 30.3 Mbits/sec
[ 5] 3.00-4.00 sec 3.45 MBytes 28.9 Mbits/sec
[ 5] 4.00-5.00 sec 3.55 MBytes 29.8 Mbits/sec
[ 5] 5.00-6.00 sec 3.53 MBytes 29.6 Mbits/sec
[ 5] 6.00-7.00 sec 3.46 MBytes 29.0 Mbits/sec
[ 5] 7.00-8.00 sec 3.62 MBytes 30.4 Mbits/sec
[ 5] 8.00-9.00 sec 3.45 MBytes 28.9 Mbits/sec
[ 5] 9.00-10.00 sec 3.60 MBytes 30.2 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 34.6 MBytes 29.0 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 34.1 MBytes 28.6 Mbits/sec receiver
And for good measure I also tested the latest commit (r7290):
Link to commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=3b11b225b32883d730a641c5aebef6f018c91649
root@OpenWrt:~# iperf3 -c ping.online.net -p 5207 -R
Connecting to host ping.online.net, port 5207
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 43702 connected to 62.210.18.40 port 5207
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 1.91 MBytes 16.0 Mbits/sec
[ 5] 1.00-2.00 sec 3.46 MBytes 29.0 Mbits/sec
[ 5] 2.00-3.00 sec 3.61 MBytes 30.3 Mbits/sec
[ 5] 3.00-4.00 sec 3.46 MBytes 29.0 Mbits/sec
[ 5] 4.00-5.00 sec 3.61 MBytes 30.3 Mbits/sec
[ 5] 5.00-6.00 sec 3.46 MBytes 29.0 Mbits/sec
[ 5] 6.00-7.00 sec 3.50 MBytes 29.3 Mbits/sec
[ 5] 7.00-8.00 sec 3.58 MBytes 30.1 Mbits/sec
[ 5] 8.00-9.00 sec 3.45 MBytes 28.9 Mbits/sec
[ 5] 9.00-10.00 sec 3.62 MBytes 30.4 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 34.1 MBytes 28.6 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 33.7 MBytes 28.2 Mbits/sec receiver
NOTE: all tests are performed with flow offload disabled!
1 Like
slh
June 20, 2018, 11:42pm
1227
It's quite relieving that it's not the switch between kernel 4.9 and 4.14 (which would have been really painful to debug), but a generic and rather isolated -stable bump instead, something that could be bisected even further.
Ansuel
June 21, 2018, 10:17am
1228
now we should check if it's related to the kernel or some wrong path refresh...
i think the culprit is in the bump to 4.14.48 (so we need to check what change between this 2 kernel version about ipq)
I just tried Kevin's 4.14.51 kernel bump patch and it seems like it fixes the issue:
root@OpenWrt:~# iperf3 -c ping.online.net -p 5207 -R
Connecting to host ping.online.net, port 5207
Reverse mode, remote host ping.online.net is sending
[ 5] local 51.175.71.139 port 40326 connected to 62.210.18.40 port 5207
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 2.39 MBytes 20.1 Mbits/sec
[ 5] 1.00-2.00 sec 6.79 MBytes 56.9 Mbits/sec
[ 5] 2.00-3.00 sec 20.5 MBytes 172 Mbits/sec
[ 5] 3.00-4.00 sec 46.3 MBytes 388 Mbits/sec
[ 5] 4.00-5.00 sec 52.4 MBytes 440 Mbits/sec
[ 5] 5.00-6.00 sec 52.5 MBytes 440 Mbits/sec
[ 5] 6.00-7.00 sec 52.5 MBytes 441 Mbits/sec
[ 5] 7.00-8.00 sec 52.6 MBytes 441 Mbits/sec
[ 5] 8.00-9.00 sec 52.7 MBytes 441 Mbits/sec
[ 5] 9.00-10.00 sec 52.1 MBytes 437 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 395 MBytes 331 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 391 MBytes 328 Mbits/sec receiver
iperf Done.
Here's the patch: https://patchwork.ozlabs.org/patch/932599/
1 Like
hnyman
June 21, 2018, 1:24pm
1230
Have I understood correctly that
4.14.44 was ok,
.48 was already bad,
current .50 is bad and
forthcoming .51 is again good.