General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports mockup
Date: Fri, 22 May 2015 10:17:25 +1000	[thread overview]
Message-ID: <CAH3Ss96Azen3eRjc0Zoj+NnxnRJwAoVvdSC8uzXu0QwLCmyKJg@mail.gmail.com> (raw)
In-Reply-To: <CAGhGL2B9wHkqWzAK-H=k8TDyugDA5axiHn=wcF+CaFWntpPkQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3571 bytes --]

It makes sense.

Or I can just have two Y-Axis with auto-scaling on both.


On Fri, May 22, 2015 at 12:26 AM, Jim Gettys <jg@freedesktop.org> wrote:

>
>
> On Thu, May 21, 2015 at 10:24 AM, Rich Brown <richb.hanover@gmail.com>
> wrote:
>
>> Ahah! I wasn't clear. I do want One Grade to Rule Them All...
>>
>> But I was only talking about different Y-axis values on the latency
>> charts, so that a bad latency in one direction doesn't hide the details of
>> the transfer in the other.
>>
>>
> ​Ah, yes.  That makes sense.
>                      - Jim
> ​
>
>
>> Rich
>>
>> On May 21, 2015, at 10:13 AM, 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
>>
>>
>> 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 #2: Type: text/html, Size: 6295 bytes --]

  reply	other threads:[~2015-05-22  0:17 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 [this message]
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
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=CAH3Ss96Azen3eRjc0Zoj+NnxnRJwAoVvdSC8uzXu0QwLCmyKJg@mail.gmail.com \
    --to=justin@dslr.net \
    --cc=bloat@lists.bufferbloat.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