<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 25/05/15 22:39, jb wrote:<br>
<blockquote
cite="mid:CAH3Ss959puqaDd917vw8gwJ-eSq10+9hMD5HO8fXytHmmiWp5Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Regarding this part:</div>
<div><br>
</div>
> <span style="font-size:13px">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 :(.</span>
<div><br>
</div>
<div>Below huge speeds, upload testing is done with web socket
now,</div>
<div>so there is a websocket address on every server now anyway.</div>
<div><br>
</div>
<div>The baseline pinging to <a moz-do-not-send="true"
href="http://dslreports.com">dslreports.com</a> doesn't seem
broken</div>
<div>but if necessary it can be changed to baseline pinging to
the</div>
<div>nearest server, wherever that is.</div>
<div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</blockquote>
<br>
Personally I might be skewed by using Firefox on Linux, I don't see
the awesome live bloat-meter, only the awesome bloat graphs.<br>
<br>
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.<br>
<br>
"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 :).<br>
<br>
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.<br>
<br>
Particularly as the "expected" low ping value shown at the start.
The 100ms server isn't even shown on the ping radar part.<br>
<br>
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.<br>
<br>
Thanks<br>
Alan<br>
<br>
<blockquote
cite="mid:CAH3Ss959puqaDd917vw8gwJ-eSq10+9hMD5HO8fXytHmmiWp5Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div class="gmail_extra">
<div class="gmail_quote">> > The elephant in my
personal room is the high latency baseline<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">
> measurement. None of the ping response time
test sites I've checked<br>
> give me anywhere near a baseline ping rtt of
100ms. Even dslreports<br>
> say "London UK is ~10ms, Google Europe is
~17ms, Dublin, Ireland, EU<br>
> is ~20ms, Frankfurt, DE, EU is ~27ms" So I
clearly don't<br>
> understand some thing(s) about this test.<br>
><br>
> Anyway, that's been an interesting 2 hours of
playing!<br>
><br>
> Kevin<br>
<br>
</div>
</div>
Good fun :).<br>
<br>
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 :(.<span
class="HOEnZb"><font color="#888888"></font></span><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>