1 probe per second IZ not enough for science! (see my forked thread)
On Sat, May 2, 2015 at 8:01 AM, Sebastian Moeller wrote:
> Hi Jb,
>
>
> On May 2, 2015, at 15:40 , jb wrote:
>
>> Each bar is an individual probe they go out once per second, which
>> determines their
>> position along the X-A
On Thu, Apr 30, 2015 at 8:10 PM, jb wrote:
> Already users are like "how can i fix this!".
>
> I've just replied to one who has lower speeds on the surfboard SB6141
> which is a modem designed for crazy cable speeds. He has an "F" and his
> downstream bloat is terrible, and upstream not much bett
Hi Jb,
On May 2, 2015, at 15:40 , jb wrote:
> Each bar is an individual probe they go out once per second, which determines
> their
> position along the X-Axis, and are tagged by color *when they come back*.
Thanks, that is exactly the information I was looking for. Given that,
I vot
Each bar is an individual probe they go out once per second, which
determines their
position along the X-Axis, and are tagged by color *when they come back*.
For the radar plot, the ones showing latencies to each location, it is
nothing to do
with buffer bloat but there are two green colors super-
Hi Jb,
I wonder the ping RTT plot, does it show all individual RTT-probes, or is it
showing an aggregate measure per bar? If aggregate which measure (hopefully the
maximum or something close like a high percentile)?
Best Regards
Sebastian
On May 1, 2015, at 08:31 , jb wrote:
> >This
This got an A+ rating, which I would not have given it, given the
enormous load spike.
http://www.dslreports.com/speedtest/400387
Imagine if your steering wheel behaved like this.
On Thu, Apr 30, 2015 at 8:10 PM, jb wrote:
> Already users are like "how can i fix this!".
The FAQ can be improved
On Thu, Apr 30, 2015 at 11:31 PM, jb wrote:
>>This got an A+ rating, which I would not have given it, given the
> enormous load spike.
>
> I think there will always be the occasional incorrectly graded test,
> this one is simply because the median of the downstream latency
> ignores the spike. If
>This got an A+ rating, which I would not have given it, given the
enormous load spike.
I think there will always be the occasional incorrectly graded test,
this one is simply because the median of the downstream latency
ignores the spike. If I used average(), then it would not ignore
the spike, h
Already users are like "how can i fix this!".
I've just replied to one who has lower speeds on the surfboard SB6141 which
is a modem designed for crazy cable speeds. He has an "F" and his
downstream bloat is terrible, and upstream not much better.
I imagine a LOT of people on slower plans have a
> On Wed, Apr 29, 2015 at 9:33 PM, jb wrote:
> ...
>> if it did get a rating it would be an "D" or "F"..
>
> How about "E" for error? That can be further explained in the text
> "Sometimes the bloat is so bad that we cannot adaquately test for it -
> and other times there is something else badly
On Wed, Apr 29, 2015 at 9:33 PM, jb wrote:
> yes it did get no rating, I don't generate ratings unless everything looks
> "right",
> meaning a decent number of down idle and up pings.
>
> http://www.dslreports.com/speedtest/377563
>
> There are only 6 latency samples during download, even though t
> 2) fq_codel with ECN enabled. Puzzled as to why this would not be an A+
Hah blame your own standards :)
The idle minimum was 66ms
The median down was +4.5ms higher
The median up was +5.5ms higher
the average of 4,5 and 5.5 is 5.0 which puts it as an "A"
but if it was a <= rather than a < it mi
1) From an OSX box over ethernet to the router.
Normal comcast blast service with no shaping:
F: http://www.dslreports.com/speedtest/394057
2) fq_codel with ECN enabled. Puzzled as to why this would not be an A+
A: http://www.dslreports.com/speedtest/394059
qdisc fq_codel 120: parent 1:12 limi
About to go try disabling the shaper here...
But I might argue for getting best results you should add buttons for
fiber cable dsl
wifi wifiwifi
Because wifi itself is so jittery, and it would be good to distinguish
ethernet results from wifi ones in your db.
On Wed, Apr 29, 2015 at 9:43
A: (fq_codel no ecn) (http://www.dslreports.com/speedtest/393466
A+ (fq_codel + ecn was enabled) http://www.dslreports.com/speedtest/393300
A: (fq_codel) http://www.dslreports.com/speedtest/393241
A: (fq_codel) http://www.dslreports.com/speedtest/391178
D: (fq_codel on the link but over wifi)
h
yes it did get no rating, I don't generate ratings unless everything looks
"right",
meaning a decent number of down idle and up pings.
http://www.dslreports.com/speedtest/377563
There are only 6 latency samples during download, even though the download
phase started at the 12 second mark and cont
Heh. Anything above a 250ms gets a F from me. But I strongly approve
of simplification to a set of grades.
http://www.dslreports.com/speedtest/378980 F, for sure.
Secondly, we tend to regard bufferbloat as one word not two.
This result got no rating. http://www.dslreports.com/speedtest/377563
O
On Wed, Apr 29, 2015 at 9:32 AM, Juliusz Chroboczek
wrote:
> Free.fr (Proxad) is certainly much better than other ISPs -- they've been
> the first to give sort-of-native (6rd) IPv6 to the masses. However,
> there's one thing that annoys me -- they have two distinct CPEs, the
> classic FreeBox (wh
Free.fr (Proxad) is certainly much better than other ISPs -- they've been
the first to give sort-of-native (6rd) IPv6 to the masses. However,
there's one thing that annoys me -- they have two distinct CPEs, the
classic FreeBox (which I have) and the FreeBox Revolution (which is
slightly less cheap
Ok thanks
I think I will stay away from the quagmire of rating ISPs on buffer bloat.
And first try to boil any bloat measurement down to an easy to understand
letter grade
between A+ and F, in a way that you guys think stands inspection of
individual
results.
On Wed, Apr 29, 2015 at 11:39 AM, Jo
my short term answer is to ask you merely collect lots more data and
slice it up different ways, trying to isolate actual browser bugs from
actual data (and NOT discarding what appears to be outliers, because
the outliers are interesting - I am perpetually thinking of the
discovery of the cosmic ba
These are pretty good questions, actually. But as pointed out, when you
want to start ranking, it's important to distinguish the performance of the
ISP itself from equipment under the subscriber's control, which itself
might be configured to hide faults in the ISP.
Statistics is a hard subject. If
On Wed, 29 Apr 2015, jb wrote:
If the tool were to list ISPs in descending order of a bloaty factor from
best (like this
one) http://www.dslreports.com/speedtest/375736
to worst (like I don't know yet), what would be the ranking factor?
I think the biggest problem is differentiating between
If the tool were to list ISPs in descending order of a bloaty factor from
best (like this
one) http://www.dslreports.com/speedtest/375736
to worst (like I don't know yet), what would be the ranking factor?
Call B the "blue" series of latencies.
Call G the "idle" series
Call O the "orange" series
https://plus.google.com/u/0/107942175615993706558/posts/ZytYb4ZkMdY
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
___
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.
25 matches
Mail list logo
