General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports mockup
Date: Thu, 21 May 2015 09:45:35 -0400	[thread overview]
Message-ID: <58264BE0-CDBE-4739-B03D-4BAA20B13997@gmail.com> (raw)
In-Reply-To: <CAA93jw6N3DmBxixxesUi4ba1isWd=uc8JGRbNEx=GBn-1nF0Rw@mail.gmail.com>

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


  reply	other threads:[~2015-05-21 13:45 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 [this message]
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
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=58264BE0-CDBE-4739-B03D-4BAA20B13997@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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