Re: [Bloat] Fwd: dslreports and inbound rate shaping

[jb <justin@dslr.net>]

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

The test, and the issue of buffer bloat, got some coverage today
in the Houston Chronicle:

http://blog.chron.com/techblog/2015/05/new-speed-test-at-dslreports/



On Tue, May 26, 2015 at 7:13 PM, Alan Jenkins <
alan.christopher.jenkins@gmail.com> wrote:

>  On 25/05/15 22:39, jb wrote:
>
>  Regarding this part:
>
>  > The baseline latency is because the bloat measurement uses a single
> websocket ping server in America.  Justin said in the forums it didn't seem
> worth the effort to set up more of them.  Seems worth an faq item though :(.
>
>  Below huge speeds, upload testing is done with web socket now,
> so there is a websocket address on every server now anyway.
>
>  The baseline pinging to dslreports.com doesn't seem broken
> but if necessary it can be changed to baseline pinging to the
> nearest server, wherever that is.
>
>
> Personally I might be skewed by using Firefox on Linux, I don't see the
> awesome live bloat-meter, only the awesome bloat graphs.
>
> PS My firefox also doesn't show the new graph-based speedtest history.  I
> disabled the obvious culprits (noscript, ghostery, ublock) & there's
> nothing on the JS console.  Happy to help if needed.
>
> "Fixing" the bufferbloat ping graph would make it more directly comparable
> to the pings on other speedtests.  I think that makes the bufferbloat point
> clearer.  Again the issue is outside the US; in the UK I see a 100ms
> "baseline".  If it's simple to start using nearer servers, that would make
> me very happy :).
>
> I agree it's not "broken".  (I also use netperf-eu at 59ms).  It's just
> confusing to interpret, if you don't already know what bufferbloat is going
> to look like.
>
> Particularly as the "expected" low ping value shown at the start.  The
> 100ms server isn't even shown on the ping radar part.
>
> If it's easier to just call out the destination country on the bufferbloat
> ping, or fudge the figures convincingly (just graph the increases from a
> minimum), that would answer my point too.
>
> Thanks
> Alan
>
>   > > The elephant in my personal room is the high latency baseline
>
>>  > measurement.  None of the ping response time test sites I've checked
>> > give me anywhere near a baseline ping rtt of 100ms.  Even dslreports
>> > say "London UK is ~10ms, Google Europe is ~17ms, Dublin, Ireland, EU
>> > is ~20ms, Frankfurt, DE, EU is ~27ms"   So I clearly don't
>> > understand some thing(s) about this test.
>> >
>> > Anyway, that's been an interesting 2 hours of playing!
>> >
>> > Kevin
>>
>>  Good fun :).
>>
>> The baseline latency is because the bloat measurement uses a single
>> websocket ping server in America.  Justin said in the forums it didn't seem
>> worth the effort to set up more of them.  Seems worth an faq item though :(.
>>
>
>

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