The issue is that Codel tries to keep the delay low, and will start
dropping when sojourn time grows above 5ms for 100ms. For longer RTT links
more delay is necessary to avoid underutilizing the link. This is due to
the multiplicative decrease - it's worst with Reno, where the halving of
cWind means that you need to have a full BDP of data in the buffer to avoid
the link going idle when cWind is halved. With longer RTTs this means more
delay than Codel allows is required to avoid a throughput hit. The worst
case happens when a single flow is controlled, but that can be a common
situation. My proposal is to sense and have the target value in Codel
automatically adjust when this worst case scenario happens - which would
mitigate most of the downside.
Simon
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 28, 2015 7:21:56 AM Eric Dumazet <[email protected]> wrote:
On Tue, 2015-07-28 at 07:11 -0700, Simon Barber wrote:
> The main danger is the negative effects on performance of using Codel. You
> may experience low throughput on high RTT links.
Really ? I've never seen this, unless you mess with codel qdisc
attributes maybe.
(Some guys seem to not really understand whole concept of a queue, and
set very low values for 'limit' attribute for example)
_______________________________________________
Bloat mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/bloat
