I am considering removing SFQ completely from the Traditional QoS implementation, and always using fq_codel. This would help simplify the webui, and also the QoS related code by making it closer to upstream.
I will probably keep the overhead settings there, tho I might consider removing them from the webui, and only keeping them available through direct nvram manipulation, as quite frankly the impact of tweaking these parameters is very minimal, and it causes more questions than it does actually help improve performance.
Can anyone think of any GOOD reason why sfq might be necessary over fq_codel?
Thanks.
I will probably keep the overhead settings there, tho I might consider removing them from the webui, and only keeping them available through direct nvram manipulation, as quite frankly the impact of tweaking these parameters is very minimal, and it causes more questions than it does actually help improve performance.
Can anyone think of any GOOD reason why sfq might be necessary over fq_codel?
Thanks.