On Sun, Jul 24, 2016 at 12:27 PM, moeller0 <[email protected]> wrote: > Hi Loganaden, > > this is exactly the right idea; interval basically defines the “reaction > time” window, or the time the endpoints of a connection minimally require to > actually react to the drop/mark signal. So on a slow link with RTTs in the > order of 300ms set interval to 300ms. > Target should be set to around 5-10% of interval to optimze the bandwidth > latency tradeoff, but in any case target should be larger than the time > required to send an individual packet, so that no queue builds up for sparse > flows. > It is not quite clear to me whether in your case you would account the long > “pipeline” depth to the target or simply bandwidth/1540… > > Best Regards > Sebastian >
Thank you ! I did the same with the OpenWRT router which is bridged with a fiber connection (30Mbit/s down, 4 Mbit/s up), and I see improvement for quality and bufferbloat: http://www.dslreports.com/speedtest/4521242 I switched from 100ms interval to 270ms interval. Now, i'm getting A+ for both. _______________________________________________ Cake mailing list [email protected] https://lists.bufferbloat.net/listinfo/cake
