Ping Optimiser does not calculate correctly

[ChrisG82]

I took a closer look at the Ping Optimiser today and noticed that it throttles more than the percentage indicated.

The test setup was as follows:
R3 freshly restarted
Optimisation performed with Ping Optimizer
Congestion control was automatically set to 99% for both upload and download
Client connected directly to R3 via cable
Speed test used: Speed Test App from Ookla with fixed server (so that the results obtained are reasonably comparable)
Maximum speed determined with "Bypass" switched on in the Speed Optimiser:

Performed several tests and achieved the following speeds on average:
Download: 270 Mbps
Upload: 43 Mbps

These values are then entered manually in R3 ("Speed Test" -> "Advanced Speed Settings")

Then deactivated the bypass in the Ping Optimiser and carried out several tests again, which resulted in the following average speeds:

Download: 238 Mbps
Upload: 38.4 Mbps

The maximum download speed was therefore limited to around 88.15 % and the upload speed to around 89.3 %.

The Ping Optimiser therefore appears to have reduced the speeds by 10% more than specified by "Congestion Control" (throttling to 89% instead of 99%)

I then simply changed the values in the "Advance Speed Settings". Here, too, the difference of approx. 10 % remains.

Set: 300 Mbps
Achieved: 265 Mbps (Just a reminder: with bypass, the maximum speed is 270 Mbps)

Can you please check whether the firmware is really just calculating incorrectly?

PS: I can provide screenshots if required.

[Netduma Fraser]

It doesn't work like that, Ping Optimizer runs tests to see what Congestion Control values would work best to keep your ping as low as possible, if you accept the results it will then change the Congestion Control percentages for you. However, you can manually adjust Congestion Control yourself but it does not impact the Ping Optimizer test results and it doesn't take your changes to the percentages into account at all. 

[ChrisG82]

The congestion control values therefore specify the percentage of the maximum available bandwidth (determined by the speed test) that may be used so that the latency does not deteriorate.

However, I determined this morning that the bandwidth is restricted about 10 % too much as specified.

[Netduma Fraser]

You setting 99% on Congestion Control does not mean Ping Optimizer will limit to that percentage, it's calculating the best values for you automatically so it doesn't consider what you have set manually

[ChrisG82]

I tried the following again: I simply entered the download value of 200 in the speed test and set it to 50% in the Conquest Control. I was then only able to use just under 90 Mbits of my bandwidth.

[Netduma Fraser]

30 minutes ago, ChrisG82 said:

I tried the following again: I simply entered the download value of 200 in the speed test and set it to 50% in the Conquest Control. I was then only able to use just under 90 Mbits of my bandwidth.

So in this instance you didn't touch Ping Optimizer at all?

[ChrisG82]

Here I made the changes while test:

[Netduma Fraser]

Could you clarify the exact steps you're doing please as I'm not following

[ChrisG82]

I know that my maximum bandwidth without restrictions is around 270 Mbps for downloads and 43 Mbps for uploads:

If I switch on the bypass, I have that too.

If I switch off the bypass, I am limited by the congestion control.

According to the setting, this should be 99% of the bandwidth. So I would be missing 1% of the bandwidth. But 10% is missing

Set the congestion control manually to 50%, 60% is missing

As I understand the function, it is there to limit the bandwidth so that there is still enough bandwidth left so that the latency is not affected if something wants to load with full bandwidth.

The bandwidth itself is determined by the setting in the speed test.

[Netduma Fraser]

Gotcha, I can reproduce that so I will pass it onto the team, thanks for the report!