General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: dave.collier-brown@indexexchange.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback)
Date: Thu, 05 Nov 2020 15:24:46 +0100	[thread overview]
Message-ID: <87wnyzswy9.fsf@toke.dk> (raw)
In-Reply-To: <b6d5e5dd-faa3-988e-1ffb-3cd8814ad3e0@indexexchange.com>

Dave Collier-Brown <dave.collier-brown@indexexchange.com> writes:

> On 2020-11-05 6:48 a.m., Toke Høiland-Jørgensen via Bloat wrote:
>
> Also, holy cow, what's going on with your connection? The unloaded
> latency says 17/110/200 min/median/max RTT. Is that due to bad
> measurements, or do you have a lot of cross traffic and a really bloated
> link? :/
>
> -Toke
>
>
> The tests differ somewhat while looking at an unloaded residential link provided by a local monopoly, Rogers Cable, and mitigated by an IQrouter (my old linksys is long dead (;-))
>
> DSLReports says
>
>   *   144.7 Mb/s down
>   *   14.05 MB/s up
>   *   bufferbloat A+
>   *   downloading lag 40-100 ms

Still a pretty big span from 40-100ms; how does that turn into an A+
score, I wonder?

> Waveform says:
>
>   *   43.47 Mbps down
>   *   16.05 Mbps up
>   *   bufferbloat grade A+
>   *   unloaded latency 93.5 ms
>
> So we're reporting different speeds and RTTs. Are we using different
> units or definitions, I wonder?

Well either that, or one of the tests is just busted. My immediate guess
would be the not-yet-released prototype is the least accurate ;)
I do wonder why, though...

-Toke

  reply	other threads:[~2020-11-05 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 21:30 [Bloat] We built a new bufferbloat test and keen for feedback Sam Westwood
2020-11-04 23:43 ` Michael Richardson
2020-11-04 23:54 ` Toke Høiland-Jørgensen
2020-11-05  1:52   ` Y
2020-11-05  0:23 ` Dave Collier-Brown
2020-11-05 11:48   ` Toke Høiland-Jørgensen
2020-11-05 13:24     ` [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback) Dave Collier-Brown
2020-11-05 14:24       ` Toke Høiland-Jørgensen [this message]
2020-11-05 16:06         ` Arshan Khanifar
2020-11-05 17:25           ` Toke Høiland-Jørgensen
2020-11-06 16:03             ` Stephen Hemminger
2020-11-06 16:17               ` Toke Høiland-Jørgensen
2020-11-06 17:05                 ` Sebastian Moeller
2020-11-08 22:07             ` Arshan Khanifar
2020-11-14  3:37               ` Dave Taht
2020-11-14 23:14                 ` Michael Richardson
2020-11-05  8:21 ` [Bloat] We built a new bufferbloat test and keen for feedback Sebastian Moeller
2020-11-05 21:30 ` Sam

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=87wnyzswy9.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.collier-brown@indexexchange.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