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
> On Jul 24, 2016, at 09:03 , Loganaden Velvindron <logana...@gmail.com> wrote:
>
> I am getting A to A+ for quality when setting the interval to 350ms.
>
> http://www.dslreports.com/speedtest/4520977
>
> I am getting - to C for quality when setting the interval to the
> default value of 100ms.
>
> http://www.dslreports.com/speedtest/4520957
_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
