[Bloat] dslreports mockup

[jb]

I did move the half-moon gauge up into the green "ping" block.

Over time the intention will be to grade a result on more than one
category, not just for buffer bloat. For example, recognition of
excessive latency to everywhere, or a poor speed compared to peers
in the same country on the same tech, or incorporation of the jitter
test result, or other yet to be determined metrics. Then an over-all
grade that is a summation of everything because people want
one answer: is my connection good or not right now, & has it got worse
over time? or better. Putting a buffer bloat grade front and centre
makes it purely a buffer-bloat test.

So I'll probably have to re-arrange the positioning of grades and so
on, and probably also have to stop calling it a "speed test" as well
because the speed race is probably over with imminent availability
of home connections faster than one can reasonably use. The median
connection speed for fios or comcast users running the test is about
50 mbit. Most of those connections are idle all day.

On Mon, May 25, 2015 at 2:58 AM, Dave Taht <dave.taht at gmail.com> wrote:

> On Sat, May 23, 2015 at 2:43 PM, Sebastian Moeller <moeller0 at gmx.de>
> wrote:
> > Hi jb,
> >
> >
> > On May 23, 2015, at 03:56 , jb <justin at dslr.net> wrote:
> >
> >> I can add error bars to the combined columns. I think that will help.
> >
> >         This is quite helpful, what exactly are the “error bars” showing?
>
> I am loving seeing the error bars. The general public won't understand
> them but a ton of other people do, and I can live with that.
>
> and loving being able to click on the bars for more detail.
>
> Aside from wanting:
>
> A) the grade center/top  as per the mockup.
> B) some more apparent indicator of the detailed graphs available (like
> rotating between them on initial view)
> C) the bloat tach front and center during the test
> D) the different number of flows tests NOT broken up by "technology"
> but by extremity, and calling out wifi VERY explicitly
> (I can do a mock up of this if my prior description was not good enough)
> E) World Peace
>
> I'm pretty happy with this (and just in awe of how much work is
> required to deploy a web browser based application)
>
> >I would vote for 2 and 98 percent qantiles.
>
> I think these are max and min, unfiltered. There are not enough
> samples in the default test (1/sec) to get higher resolution (although
> I run the hires bloat test and would certainly prefer that a minimum
> of 100ms sampling rate was used for all - 20ms would be better). But 2
> and 98 if possible would be better than max/min, (with sufficient
> samples).
>
> http://en.wikipedia.org/wiki/Seven-number_summary is fun because it
> depends on a normally distributed model, which this stuff isn't. (I'd
> like to see this for flent, also)
>
> I would like to see the algorithm(s) for this documented sufficiently
> somewhere... (and to finish duplicating the work in flent)
>
> >I note that I have seen several times that both error bars (low and high)
> of the idle category seems to be displayed above the bar, like levitating
> above the bar. Could be display error on my end, but I guess the bars show
> something meaningful and I just do not know how to parse it correctly…
> >
> > Best Regards
> >         Sebastian
> >
> >>
> >> On Sat, May 23, 2015 at 10:55 AM, David Lang <david at lang.hm> wrote:
> >> On Thu, 21 May 2015, Jim Gettys wrote:
> >>
> >> Providing separate grades for upload and download does not make sense to
> >> me, as interference with acks in the other direction badly hurts that
> >> traffic. Uploads and downloads are *not* independent variables.
> >>
> >> KISS: one grade....
> >>                  - Jim
> >>
> >> yes and no.
> >>
> >> If I am getting a bad grade, will replacing my local router help? or is
> all the problem on the ISPs equipment?
> >>
> >> having upload getting an A+ due to running good, debloated systems
> locally, but the download getting a F due to the ISP buffering would be
> meaningful.
> >>
> >> David Lang
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat at lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat at lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >>
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat at lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat at lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20150525/fbe9e6a6/attachment-0003.html>