@stephenw10 I've tried this with no success.
I'm running HFSC because it's the only way to maintain a stable connection for the entire facility, avoiding sudden drops, poor meeting quality and all sort of things that the network administrator will be blamed of.
The examples above are real.
Follow below my TS configuration and to justify the reason I built this configuration, the parameters was based on speed metrics running on an empty facility, no link usage at all.
I can only reach near 50% of the down speed.
-wan1 hfsc 350Mb
-qInternet queue limit 500 bw 330Mb ul 330Mb ls 330Mb
-qDNS queue limit 500 sched codel bw 5% ls 5%
-qBulk queue limit 600 sched codel bw 26% ls 26%
-qACK queue limit 500 sched codel bw 20% rt 20% ls 20%
-qVoip queue limit 50 sched codel bw 5% rt 5% ls 5%
-qMeet queue limit 300 sched codel bw 27% rt 27% ls 27%
-qTech queue limit 500 sched codel bw 4% ul 100Mb ls 4%
-qLive queue limit 500 sched codel bw 2% rt 2% ls 2%
-qDefault queue limit 500 sched default codel bw 10% ls 10%
-lan hfsc 350Mb
-qInternet queue limit 500 bw 330Mb ul 330Mb ls 330Mb
-qDNS queue limit 500 sched codel bw 5% ls 5%
-qBulk queue limit 600 sched codel bw 26% ls 26%
-qACK queue limit 500 sched codel bw 20% rt 20% ls 20%
-qVoip queue limit 50 sched codel bw 5% rt 5% ls 5%
-qMeet queue limit 300 sched codel bw 27% rt 27% ls 27%
-qTech queue limit 500 sched codel bw 4% ul 100Mb ls 4%
-qLive queue limit 500 sched codel bw 2% rt 2% ls 2%
-qDefault queue limit 500 sched default codel bw 10% ls 10%
All queues and floating rules was built on bare hands without the wizard usage.
Please let me know if I can provide any more configurations.
Thank you.