From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports mockup
Date: Thu, 21 May 2015 21:46:01 +0000 [thread overview]
Message-ID: <299F8BEE-AEF2-4C2F-B197-F8C7E409C275@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAGhGL2AzCpagXqaLkud-f6Abjbs1PGQFe649J8-yd=L+uELZ5A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3786 bytes --]
> On 21 May 2015, at 15:23, Jim Gettys <jg@freedesktop.org> 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
As a dumb user I agree with the one overall grade result. As a slightly less dumb user seeing up & down graphs is useful for tuning bandwidth limits, or I found it so at least. It's suddenly struck me as odd that a test section & graph for simultaneous up & down streams isn't included, presumably it would also be the basis for the one grade overall badge result. I guess that's feedback to dslreports if they're not already listening here.
Agree with Rich's comments re: background colours following scaling as a further pointer to bad/better/good on up/down latency differences.
Kevin
PS: As an aside I don't know if my comments/thoughts are helpful on this list or not. I know there are a lot of extremely experienced & clever people here who've been battling this problem for a long time and I fear 'stupid' questions will just try people's patience. If my dumb user observations aren't helpful please tell me to shut up!
>
>
>> On Thu, May 21, 2015 at 9:45 AM, Rich Brown <richb.hanover@gmail.com> wrote:
>> That is interesting. I'm trying to think how the latency charts could be misconstrued, since a Y-axis on the right isn't the norm - I don't think it's hard to understand, but just different.
>>
>> The display as-is clearly shows that the download is badly bloated, but the upload is fine. That's the important message for most people at home. But as a researcher, you want to understand the details of the upload. So having different scales would help you see better into the problem.
>>
>> * If the download and upload values are substantially similar, the left and right Y-axis scales should be the same, so there wouldn't be confusion
>>
>> * If the values are substantially different (as in this screen shot), the pink and yellow backgrounds (on the left) and the lack of them on the right would provide a solid cue that there is something different going on between the two charts.
>>
>> * On the other hand, the report already shows different Y-axis values for the down/upload speeds, so the latency charts could mimic the speeds...
>>
>> Other thoughts?
>>
>> Rich
>>
>> On May 20, 2015, at 12:46 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> > I wanted to be able to have separated charts for up and down on
>> > different scales, so I took apart what exists today in gimp and got
>> > this:
>> >
>> > http://snapon.lab.bufferbloat.net/~d/dslreportsmockup.png
>> >
>> > I guess it is partially because I am getting a C on the download at
>> > this speed, and no A+ on the upload, and I would at least like to get
>> > a gold star from teacher for effort. :/
>> >
>> > I dunno how to fix the download short of getting rid of several
>> > seconds of inherent buffering in their CMTS. There must be a simple
>> > way to do that??
>> >
>> > --
>> > 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.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
[-- Attachment #1.2: Type: text/html, Size: 5843 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3089 bytes --]
next prev parent reply other threads:[~2015-05-21 21:46 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 [this message]
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
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=299F8BEE-AEF2-4C2F-B197-F8C7E409C275@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/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