[Feature Request] GUI and manuel settings for Queue Management (especially with CAKE)

[Plyra]

I like my Keenetic Giga since day 1 and I'm using nearly every feature it has. So I look forward and I'm requesting one more feature from our successful development team

Some other routers and nearly every open source modem firmware (e.g. OpenWrt, Tomato) has some sort of GUI for packet management to fight with Bufferbloat effectively. I know we can set fq_codel and CAKE somehow with command line. Also we can use QoS for management. But in the end, both are not so effective so can you add some sort of menu to setup queue management? I'm on 3.7 Alpha 12 and even latest priority settings are not enough against Bufferbloat. Being able to setup queue management manually would be pretty helpful for gamers and it helps IPTV users for smoother online video playback.

I really appreciate any fix you can provide and I'm ready to test any build for this matter.

[ndm]

14 minutes ago, Plyra said:

I'm on 3.7 Alpha 12 and even latest priority settings are not enough against Bufferbloat

Still not enough information: how you are testing, what is your current measurable result, and what is your expectation.

Have you tried to change priorities in the `controlPanel/intelliQoS` menu?

[Plyra]

Actually I did tons of test with DSLReports speed test. I tried different variations (with ntce enabled, disabled, only IntelliQoS enabled, only priority 1-2-3-...-6 for testing device connected with Cat6, IntelliQoS enabled + priorities and much more)

My ISP provides 100 Mbps for me but since it's fast ethernet I can only reach 95 Mbps which is fine for me. After tons and tons of testing (as you can see) I think my best bet is disabling every setting (therefore no IntelliQoS and default priorities).

Default settings (no speed limit, no IntelliQoS, default priorities)

I tried IntelliQoS and changing priorities but they were ineffective, gave me similar results.


I got best results with limiting speed only (like 94000/8000 kbps, no IntelliQoS, default priorities) so I wildly guess that speed limiting somehow enables queue management.


I don't say these results are bad. It is fine actually. But my older garbage tier ISP modem did it better without any config (no tests since I don't own it anymore) so I expect that Keenetic can do it much better.

Изменено 12 июня, 2021 пользователем Plyra

[ndm]

9 minutes ago, Plyra said:

I don't say these results are bad. It is fine actually. But my older garbage tier ISP modem did it better without any config (no tests since I don't own it anymore) so I expect that Keenetic can do it much better.

Thanks for sharing! The QoS feature is still work in progress. Your connection type is more complicated than DSL, for example, because currently QoS requires information about your ingress speed. (DSL naturally "knows" the downlink speed.) I hope we implement the auto-ingress algorithm that is planned for 3.07.

[Plyra]

2 minutes ago, ndm said:

Your connection type is more complicated than DSL, for example, because currently QoS requires information about your ingress speed. (DSL naturally "knows" the downlink speed.) I hope we implement the auto-ingress algorithm that is planned for 3.07.

Oh, nice to hear  What about egress then? Uplink is pretty important nowadays so I hope QoS will be able to fix it smartly.

I want to ask something, do you plan adding this kind of menu? Everyone like automatic algorithms, they help much but I'd rather manually set things. That is exactly what I want actually.

[Le ecureuil]

В 12.06.2021 в 15:13, Plyra сказал:

Oh, nice to hear  What about egress then? Uplink is pretty important nowadays so I hope QoS will be able to fix it smartly.

I want to ask something, do you plan adding this kind of menu? Everyone like automatic algorithms, they help much but I'd rather manually set things. That is exactly what I want actually.

You can achieve the same result by enabling shaping on the Home segment. Shaper uses cake (and of course priorities) inside.

[Plyra]

4 hours ago, Le ecureuil said:

You can achieve the same result by enabling shaping on the Home segment.

Do I need to limit their speed to shape traffic? I upgraded to Alpha 13 today and did some tests. no speed limit + service class 1 gives me not-so-good results.



Graphic for bufferbloat, idle latency was 50 ms and while uploading it was 186 (avg) so service classes won't help us much.



So, without limiting speed, we actually CAN'T achieve same results 😕

Now let's limit some speed with Shaper. No priorities, no QoS. My ISP provides 100/8 so limits are fine I guess.




As you can see, we got much better results. There is nearly no difference between idle latency (49 ms) and latency (52 ms) while uploading. So I guess Shaper somehow only manages while uploading, not downloading. I tried other limits for download speed (like 90 Mbps and 85) and gave me similar results. So, without Keenetic implements a fix for Shaper to manage download speed, we CAN'T achieve same or better results.