I am curious to peoples & MikroTiks thoughts around best practice for Queue configuration.
We terminate a large number of customer VPLS circuits back to a MikroTik in one of our POPs. We implement a simple queue at the egress interface for each circuit.
My question is whether its best to configure a single simple queue for each bandwidth limit and then just add targets as required or should I set up a single queue for each circuit
All of our queues are setup and limited by ip addresses, usually /24 or /23.
Could you do the same, unless you are limiting each connection differently then I could see why you are doing it by connection.
I would suggest if your connection limits are similar, if you only have 2-3 different types, then you would utilize targets.
Less rules to managed is always better.
To piggy back your question, what would be the best practice for utilizing queues across a routed network.
Currently the core router currently manages all the queues and the routed networks do nothing, besides OSPF and a few firewall rules for external protection.
Should the queues be brought locally to the routed networks?
The reason is there was a recent DOS or some kind of flooding that took place on one of the routed links and if the queues were local it may have prevented it.
Thoughts?
At MUM US 2014, Uldis from MikroTik stated that as of v6.19, simple queues handling is such that the router will distribute individual queues across all CPU cores available in the system. Thus, if you’re using a multi-core unit (such as a CCR), you should set up separate simple queues for each circuit, so the system can load balance queuing functionality optimally.