10-09-2018 02:10 PM
Please incldue iPerf3 fucntionality. This would help me and other community members to properly test throughput of UniFi APs. At least the server capability to start with. iPerf is BSD.
I have tried various apps on iOS and Android to good results so far, but my fear is most of them are becoming outdated.
Here is one of the apps: https://itunes.apple.com/us/app/wifiperf-endpoint/id909661121?mt=8
10-14-2018 09:10 AM
Another advantage is iPerf3 is that it can be run on a mobile client as "server mode" with -s switch on many clients with a centralized test runnner such as UAS XG. You can see what I am talking about here: https://community.ubnt.com/t5/UniFi-Wireless-Beta/UniFi-Signal-and-Throughput-Tests/m-p/2192979
My fear is that the current clients that I am using on my mobile devices are becoming outdated and are missing some important bug fixes. This will make speed test results less accurate and reliable.
I have also talked to @UBNT-Jonge about incorporating this into UniFi app as well, however, it would help to have in either or both of the apps.
10-15-2018 03:40 AM
@Jardin_Espanol Got it - we want to have WiFiman as simple as possible so it's attractive also to non-advanced users. If we add advanced features like tcp window size and number of streams, then we would need to find a way how to automatically interpret results to all users in simple way. If we can do that then we would certainly consider to add these features.
10-15-2018 09:07 PM
10-16-2018 02:52 AM
What analytics do you do when you change TCP window size or number of streams? How do you interpret the results? Since you use it in your measurement, it probably gives you some information about network. Can you share that?
10-16-2018 09:07 PM - edited 10-28-2018 07:48 PM
I am playing around with number of streams and TCP Wndow to maximize the Bitrate while lowering the Retry value.
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 300 second test, tos 0 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-5.00 sec 317 MBytes 531 Mbits/sec 511 731 KBytes [ 5] 5.00-10.00 sec 306 MBytes 514 Mbits/sec 52 823 KBytes [ 5] 10.00-15.00 sec 306 MBytes 514 Mbits/sec 31 888 KBytes [ 5] 15.00-20.00 sec 309 MBytes 518 Mbits/sec 24 1.00 MBytes [ 5] 20.00-25.00 sec 312 MBytes 524 Mbits/sec 10 1.09 MBytes [ 5] 25.00-30.00 sec 314 MBytes 526 Mbits/sec 99 1.19 MBytes [ 5] 30.00-35.00 sec 308 MBytes 516 Mbits/sec 168 670 KBytes [ 5] 35.00-40.00 sec 304 MBytes 510 Mbits/sec 28 735 KBytes
At this point it would still be helpful to just have the server/endpoint (the -s swtich) part available for testing. I don't need full functionality for every command line switch that is available in iPerf3, since I can control all the tests from my UAS XG. So instead of running rest from mobile client to UAS XG, I can run tests from UAS XG to the mobile client and use the -R switch when needed.