On Tue, Apr 24, 2018 at 4:17 AM, Sebastian Moeller <[email protected]> wrote:
> That is true to some degree, but the overall algorithm is not that hard: Set the shaper at 50% of contracted rate and measure the bufferbloat (depending on the expertise of the user either via flent or the dslreports speedtest); if bufferbloat acceptable set shaper higher (by 50% of the remaining difference to 100% contracted rate) or if unaceptable lower. Really just a binary search for the acceptable limits. Now this should be done individually for each shaper direction. The final proof of the pudding is to see how this shaper copes with a bi-directional saturating load (like flent's rrul). Given that the target audience is VCR-owning home users could this be reduced to a scripts? Then perhaps hardware vendors could then expose it in their GUI. /john
_______________________________________________ Cake mailing list [email protected] https://lists.bufferbloat.net/listinfo/cake
