01-10-2017 03:49 PM - edited 03-08-2019 08:52 AM
Meaning if I use "priority percent 80" when I really only need 30%, does that have any negative affect? Is it best practice to use the smallest possible number (maybe 35 or 40 in this example) for a PQ to keep latency and jitter at its lowest? I saw a recommendation elsewhere to keep the queue size low for the best latency/jitter results, so I was curious if this was true. I couldn't find any specific cisco docs stating either way.
Solved! Go to Solution.
01-10-2017 05:12 PM
Well, I guess you could make the priority queue huge. The impacts would be if traffic in the priority queue was much larger than expected (say something goes wrong) it will starve other traffic. Also by allocating 80% to one class you don't leave much to give other classes.
Typically you would make it the size of the expected traffic plus sometimes a little bit more for head room.
For example, if you wanted to support 4 concurrent 96Kb/s streams (being 64Kb/s for codec and 32Kb/s for the IP overhead) you would make it around 384Kb/s.
01-10-2017 05:12 PM
Well, I guess you could make the priority queue huge. The impacts would be if traffic in the priority queue was much larger than expected (say something goes wrong) it will starve other traffic. Also by allocating 80% to one class you don't leave much to give other classes.
Typically you would make it the size of the expected traffic plus sometimes a little bit more for head room.
For example, if you wanted to support 4 concurrent 96Kb/s streams (being 64Kb/s for codec and 32Kb/s for the IP overhead) you would make it around 384Kb/s.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide