Mikrotik: queues without bandwidth limit?

Question

Computer networks

Good afternoon, colleagues!

I have been successfully working with Mikrotiks for quite a long time, but today a question arose that I managed to confuse.
Until today, the issue of prioritizing traffic and limiting the bandwidth of the channel was based on a stable (plus or minus half a megabit) speed.

And now I have an extremely unstable channel, but I want to at least divide the traffic according to priorities without cutting the bandwidth.

In other words, will the division into 1 and 8 priorities really work with such rules?

/queue tree add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 name=qos_1 packet-mark=qos_1 parent=global-total priority=1
/queue tree add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 name=qos_8 packet-mark=qos_8 parent=global-total priority=8

Answer 1

And how do you imagine it from an algorithmic point of view?
Any traffic prioritization policies come into play when the queues on the interfaces are full and you have to make a choice which of the packets will survive and which will not. Either the physical interface is overloaded, or a shaper has been applied to limit the bandwidth. If the channel is not overloaded, then all arriving packets go out without fuss. How do you imagine prioritization in conditions when everyone is fine and everyone fits perfectly into the channel? Drop non-priority classes? “Unstable channel” = “losses somewhere at the provider”, uncontrollable, unpredictable ...

Answer 2

Use the PCQ queue type.

Answer 3

In all sorts of howtos, it was usually recommended to set the shaper to a speed slightly less than the physical speed and already prioritize inside.