i believe that most Mikrotik users depend on Megis QOS in Managing the networks QOS but for months of testing and using Megis policy "that i found it the best choice " the users faced haigh latency when they download files or browse normal web sites like youtube , facebook .. etc and this is affect on the over all performance of the service delivered to the end user , bellow my config
I looked over your queues, didn’t have a lot of time to go over it well.
This is what I use, probably an older version. Essentially, the first 2MB is priority of 4, after that it drops to 7. This keeps latency fairly level. Obviously, tune to your own requirements.
I did not include the L7 info. I can provide that if needed. This may be incomplete.
/ip firewall mangle add chain=forward protocol=tcp action=mark-connection new-connection-mark=new_conn passthrough=yes comment="mark all new connections" disabled=no
/ip firewall mangle add chain=forward protocol=tcp connection-mark=new_conn connection-bytes=0-2000000 action=mark-packet new-packet-mark=new_packet passthrough=no comment="mark packets" disabled=no
/ip firewall mangle add chain=forward protocol=tcp connection-mark=new_conn action=mark-packet new-packet-mark=old_packets passthrough=no comment="marking old packets" disabled=no
/queue type add name="PCQ_Upload" kind=pcq pcq-rate=0 pcq-limit=50 pcq-classifier=src-address pcq-total-limit=2000
/queue type add name="PCQ_Download" kind=pcq pcq-rate=0 pcq-limit=50 pcq-classifier=dst-address pcq-total-limit=2000
/queue tree add name="Main_Upload" parent=global-in packet-mark="" limit-at=0 queue=PCQ_Upload priority=8 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="4 Up First 2Mbyte" parent=Main_Upload packet-mark=new_packet limit-at=256000 queue=PCQ_Upload priority=4 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="7 Up Rest Mbytes" parent=Main_Upload packet-mark=old_packets limit-at=256000 queue=PCQ_Upload priority=7 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="Main_Download" parent=global-out packet-mark="" limit-at=0 queue=PCQ_Download priority=8 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="4 Down First 2Mbyte" parent=Main_Download packet-mark=new_packet limit-at=256000 queue=PCQ_Download priority=4 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="7 Down Rest Mbytes" parent=Main_Download packet-mark=old_packets limit-at=256000 queue=PCQ_Download priority=7 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="ICMP" parent=APBridge packet-mark=icmp_pack limit-at=0 queue=default priority=3 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="8 Down P2P" parent=Main_Download packet-mark=p2p_pack limit-at=64000 queue=PCQ_Download priority=8 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="8 Up P2P" parent=Main_Upload packet-mark=p2p_pack limit-at=64000 queue=PCQ_Upload priority=8 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="1 SIP Down" parent=Main_Download packet-mark=sip_pack limit-at=256000 queue=PCQ_Download priority=1 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
/queue tree add name="1 SIP Up" parent=Main_Upload packet-mark=sip_pack limit-at=256000 queue=PCQ_Download priority=1 max-limit=50000000 burst-limit=0 burst-threshold=0 burst-time=0s
Mikrotik doesn’t have low latency prioritization. To be honest, I didn’t see any effectiveness of the current prioritization system.
You could show your interest in the LLQ (Low Latency Queueing) feature implementation here: http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/Feature_Requests
You have PCQ Down main, then 4 sub queues below that.
Say you have 10Mb, you want to set the main down at 10Mb, SIP traffic to whatever is appropriate, if you have lot of users, probably 7Mb. For your first down or up, set it to 9500k, for the down rest set it to 8Mb or so, P2P set whatever you wish. Do the same for your upload, say main is 1Mb, first is 900k, rest is 800k, etc.
You can tweak this to your network and your specific needs. Basically you want to never quite use all of your bandwidth. You can set the “rest” down and up higher or lower, just make sure one sub queue can never fill the main queue.
i’m talking on different scenario , what i’m doing is limit the users into classes , "Economy class , Standard Class , business and super "each user will get the rate “Speed” of the specific class , and the Total Queue in tree is unlimited so the priority u talk about will not work .
i do understand that my config will not improve that , and even all other QOS standard and optimized config will not do , i believe it related to Mikrotik QOS standards , i think Queues need some big changes by mikrotik to give better performance .
Any progress on this issue ?
I saw, that even a long Filter list causes latency. ( tried it on different RB-Hardware upto RB1100AHx2) @engineertote: do you use other hardware ?
I believe I can come up with a Queue Tree that has PCQ for user max-limit just in its low priority part so that we achieve QoS for some of users packets while treating the rest “download” packets in an equal (PCQ) best-effort (discard as we see fit) way. I will publish it here http://wiki.mikrotik.com/wiki/NetworkPro_on_Quality_of_Service in the coming days
