Ansuel / tch-nginx-gui

Modified file to apply to a stock technicolor GUI
GNU General Public License v3.0
343 stars 52 forks source link

DGA4132 Priority device increase bufferbloat #923

Open Edoardo001 opened 4 years ago

Edoardo001 commented 4 years ago

NB: Before submitting an issue, check if there is one already open that suits the problem you are having!

If you are on the latest dev, please go to Cards >> System Extras >> Debug Report and press the Generate button. Please attach the file here:

Device Model: DGA4132 Gui Version: 9.5.38-ba81e28c

Description of problem:

How to reproduce (if possible): in card "device" set priority to "priority" ad in this test "http://www.dslreports.com/speedtest " bufferbloat in upload fase will raise as hell.

Media/Photos (if possible):

FrancYescO commented 4 years ago

missing firmware version. putting it back to normal get will "solve" the issue ?

Edoardo001 commented 4 years ago

missing firmware version. putting it back to normal get will "solve" the issue ?

Version is 18.3.k Cobalt, scuse me i miss that. Putting back to normal solve the issue. However is since yesterday that I use this gui, is freaking awesome, hope to try this feature in a next build.

Dark4Codrutz commented 3 years ago

AGTHP_2.2.1 I can reproduce: Normal priority: http://www.dslreports.com/speedtest/68248304 (~http://www.dslreports.com/speedtest/68247940~ slight different servers, same results though) Priority enabled: http://www.dslreports.com/speedtest/68248185

With Priority the Upload bufferbloat explodes. Indeed this technique is well known to be counter-productive even if it was meant to maximize throughput and deal with tcp congestion when the network is crowded, so the Priority behaviour might be by design.

My test run wasn't in a busy network time so it reached the upper limit of my upload speed in both instances. Would be interesting to run this test using a second device jamming the upload of the network and see if there would be any noticeable improvement for the 'Prioritized' device

Edit: After reading 3c04d11 my impression is that this feature was intended to minimize latency (given by the naming of GamingPriority) rather than maximize/prioritise throughput in QoS. Well, in that case this is a really unintended bug.