General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports mockup
Date: Fri, 22 May 2015 12:33:36 -0700	[thread overview]
Message-ID: <CAA93jw41CLQPhrHiBhabWqGnp-4sE3-ttptPpHvMbD2qWoWZ3Q@mail.gmail.com> (raw)
In-Reply-To: <CAH3Ss958mM1mpFb=qe72qmY8jYCksNDyjX1MxLOnwGjGrYQWnA@mail.gmail.com>

On Fri, May 22, 2015 at 12:00 AM, jb <justin@dslr.net> wrote:
> Well the dual Y-Axis thing didn't work.
> It would require removal of the color bands and looked confusing.

k.

> So I've done a drill-down thing instead. You get just three bars, then can
> drill into each by clicking, to see an expansion against its own Y-Axis.
> Hard to explain, easier to see:
>
> http://www.dslreports.com/speedtest/525965

1) It shows "series 2" for the drill downs rather than upload/download/idle.

2) I am not big on averages, period. showing min/median/max on the bar chart
is more satisfying to me, (see relevant netperf-wrapper plottype), but I know
that too is confusing to users.

Saying "average bloat" is sort of like saying this drug only kills 2%
of people on average - it might be accurate statistically (except for
missing a long term trendline and not coping with different RTTs
well), but it does tend to matter to those it kills.

I know tons of people like plain old bar charts, but...

3) I like how this drilldown and the previous detailed graphs shows
the queues building over the course of the test. This lends intuition
to the problem (and shows the trendline in particular)

Perhaps something that would be interesting would be for the drill
down to instead
swap between graphs over an interval (every few seconds), then stop on the
worst one after 20 seconds....

going back to the first screen of the test actually running:

4) The radar ping plot is boring after the test starts, and on a small
laptop the bufferbloat
"tach" is invisible. I would remove the radar ping plot after the test
starts and stick the
bloat tach there instead.

Aint I demanding?

5) (this is still marvellous work and deepest gratitude, and so on,
and thanks for playing with us)

6) we are so losing on inbound at the moment.

http://www.dslreports.com/speedtest/529300

7) I hope to add some tests to the finally renamed flent (formerly
netperf-wrapper) that will more closely duplicate your tests. In
particular, I want to add support for many different remote servers to
all the basic tests. You have clearly pointed out that we need to
tackle that,  and see items 5, and 6...

Are you settled on 16/6 for the basic "cable" test, in particular?


> On Fri, May 22, 2015 at 10:56 AM, Jonathan Morton <chromatix99@gmail.com>
> wrote:
>>
>>
>> > On 22 May, 2015, at 03:17, jb <justin@dslr.net> wrote:
>> >
>> > Or I can just have two Y-Axis with auto-scaling on both.
>>
>> You could also try a square-root scale (as opposed to linear or
>> logarithmic).  This should help with comparing data with different orders of
>> magnitude, without flattening things as aggressively as a log scale.
>>
>> But perhaps we should see what it looks like before committing to it.
>>
>>  - Jonathan Morton
>>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@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

  parent reply	other threads:[~2015-05-22 19:33 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 [this message]
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=CAA93jw41CLQPhrHiBhabWqGnp-4sE3-ttptPpHvMbD2qWoWZ3Q@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --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