We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.

Return to Answer

Formatting for readability, some spelling

edit approved Oct 8, 2015 at 20:33

699
9
21

You should chose acceptable queeningqueueing latency basing on type of traffic. For example, for voice queuing more that 200ms is already a problem. While having 500ms buffer for ftp/torrent traffic is not a big problem at all.
Queuing latency/strategy is a question of traffic type not interface speed. For example VOIP, perhaps, should not be queued at all. Unfortunately tc RED documentation is not very clear, you would better read some RED info on Juniper/Cisco site and apply that knowledge to tc.

For example, for voice queuing more that 200ms is already a problem.

While having 500ms buffer for ftp/torrent traffic is not a big problem at all.

Queuing latency/strategy is a question of traffic type not interface speed. For example VOIP, perhaps, should not be queued at all. Unfortunately the tc RED documentation is not very clear, you would better read some RED info on Juniper/Cisco site and apply that knowledge to tc.

answered Dec 12, 2013 at 19:21

146
3

You should chose acceptable queening latency basing on type of traffic. For example, for voice queuing more that 200ms is already a problem. While having 500ms buffer for ftp/torrent traffic is not a big problem at all.
Queuing latency/strategy is a question of traffic type not interface speed. For example VOIP, perhaps, should not be queued at all. Unfortunately tc RED documentation is not very clear, you would better read some RED info on Juniper/Cisco site and apply that knowledge to tc.