From: Sebastian Moeller <moeller0@gmx.de>
To: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports mockup
Date: Sat, 23 May 2015 23:43:05 +0200 [thread overview]
Message-ID: <D3A5AD9B-1E10-44D5-A4D4-0F6A26C42A3B@gmx.de> (raw)
In-Reply-To: <CAH3Ss96EuT5mFt7juTDky5e1_0GnjbC1b9PUVHQYz3i0CE2usg@mail.gmail.com>
Hi jb,
On May 23, 2015, at 03:56 , jb <justin@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 would vote for 2 and 98 percent qantiles. 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@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@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2015-05-23 21:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 16:46 Dave Taht
2015-05-21 13:45 ` Rich Brown
2015-05-21 14:13 ` Jim Gettys
2015-05-21 14:24 ` Rich Brown
2015-05-21 14:26 ` Jim Gettys
2015-05-22 0:17 ` jb
2015-05-22 0:56 ` Jonathan Morton
2015-05-22 7:00 ` jb
2015-05-22 10:03 ` Sebastian Moeller
2015-05-22 12:52 ` jb
2015-05-22 17:46 ` Kevin Darbyshire-Bryant
2015-05-22 19:30 ` Sebastian Moeller
2015-05-22 19:33 ` Dave Taht
2015-05-21 21:46 ` Kevin Darbyshire-Bryant
2015-05-23 0:55 ` David Lang
2015-05-23 1:56 ` jb
2015-05-23 19:35 ` Kevin Darbyshire-Bryant
2015-05-23 21:39 ` jb
2015-05-23 21:43 ` Sebastian Moeller [this message]
2015-05-24 16:58 ` Dave Taht
2015-05-25 4:07 ` jb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3A5AD9B-1E10-44D5-A4D4-0F6A26C42A3B@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=justin@dslr.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox