Re: [Cake] cake work needed for openwrt merge

[Benjamin Cronce <bcronce@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

On Tue, Sep 8, 2015 at 2:20 AM, Sebastian Moeller <moeller0@gmx.de> wrote:

> Hi Benjamin,
>
>
> On Sep 8, 2015, at 00:31 , Benjamin Cronce <bcronce@gmail.com> wrote:
> > [...]
> > It may be easier to use a distance based naming. Instead of something
> like "High(250ms) RTT" be like "Inter-continental", medium(100ms) RTT may
> be "Intra-continental", and low(50ms) RTTs may be "Local Region". "Region"
> can be a bit ambiguous, but I figured if given two options "Local Region"
> and "Intra-continental", that the idea of what "region" represents in this
> context is clear enough. Satellite links would only need one option because
> the latency of the satellite will be greater than the latency from all of
> the terrestrial links combined. As for the actual variable name and not the
> option names. hmmm. Assuming similarly named options, "Optimize for"?
> > [...]
>
> For the crowd on this mailing list any names will do, but for novices that
> just heard of buffer bloat and its remedies, I believe we need simple
> unambiguous names. The challenge with distance is that while geographical
> distance should not be too hard to figure out, path distance is much
> trickier (aka true user will need i measure). If I recall correctly, codel
> is actually pretty robust against deviations of true RTTs from interval,
> but I do not remember any data showing this on a per true RTT basis or for
> fq_codel (where I assume the issue might be more pronounced, as the
> different RTT flows will be separated unlike in codel where all is mixed).
>
>
> Best Regards
>         Sebastian


You point out that the path distance is more important than geological
distance, which I find interesting because in my case, my max ping to any
fiber linked place on Earth is almost exactly 250ms. Assuming 0.6c for
light in fiber, that's 27,900 miles round trip. The Earth has a maximum
circumference of 24,901 miles. That means route distance is within 12.5% of
geological distance. I find latency to be a very good indication of
geological distance. You did mention that you found my latencies
"interesting". I have a feeling I have a special circumstance.

Watch people narrow down where I live based on those listed latencies. At
least I did some mild rounding.

[-- Attachment #2: Type: text/html, Size: 2900 bytes --]