Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Wes Felter <wmf@felter.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Fixing bufferbloat: How about an open letter to the web benchmarkers?
Date: Fri, 12 Sep 2014 14:11:32 +1200	[thread overview]
Message-ID: <CAKiAkGT0wq7Szs8nbjAPJB0C_uOCzZgY7m0A-CGC1Dpt9URB4A@mail.gmail.com> (raw)
In-Reply-To: <5E98060D-99DE-4671-A574-4A104BA8D952@gmail.com>

The tendency has been (I am also guilty of this) to go down the route
of  'here I made this $bandwidth test' using some
$combination_of_scripts  - tell users to use this It's better and more
reflective of what users should be testing for"

That route is the one I am kinda trying to steer away from, as it
isn't solving the issue. Which is IMHO a user education one.

But yes you are right, you would have to solve this for each and every
measurement site out there, or at the least - the most popular one in
your particular market.

NZ has other challenges in that things like Speedofme are useless for
us because there are no test servers anywhere near our international
IX's and even on 1Gbit machines right on the Global gateway I get
nothing better than 20-30mbit out of it. (TCP BDP is a bitch in NZ).


-Joel

On 12 September 2014 14:04, Jonathan Morton <chromatix99@gmail.com> wrote:
>
> On 12 Sep, 2014, at 4:49 am, Joel Wirāmu Pauling wrote:
>
>> So if ookla implemented a udp based test, changed it's statical weighting and data mining methods overnight. At least in NZ that might help.
>
> Isn't that the whole point of this discussion?
>
>  - Jonathan Morton
>

  reply	other threads:[~2014-09-12  2:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 16:03 [Cerowrt-devel] " Dave Taht
2014-09-11 16:35 ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2014-09-11 18:19 ` [Cerowrt-devel] " Maciej Soltysiak
2014-09-11 18:33   ` David Personette
2014-09-12  0:13 ` [Cerowrt-devel] [Bloat] " Rich Brown
2014-09-12  0:35   ` dpreed
2014-09-12  0:42     ` Jonathan Morton
2014-09-12  1:24       ` dpreed
2014-09-12  1:49         ` Joel Wirāmu Pauling
2014-09-12  2:04           ` Jonathan Morton
2014-09-12  2:11             ` Joel Wirāmu Pauling [this message]
2014-09-12  1:48       ` Rich Brown
2014-09-12 15:24         ` Rick Jones
2014-09-13  0:19           ` David P. Reed
2014-09-12  7:17   ` Jesper Dangaard Brouer
2014-09-12 12:16     ` Rich Brown
2014-09-12 12:55       ` Jesper Dangaard Brouer
2014-09-12  0:31 ` [Cerowrt-devel] " dpreed
2014-09-12  9:44 ` Toke Høiland-Jørgensen

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKiAkGT0wq7Szs8nbjAPJB0C_uOCzZgY7m0A-CGC1Dpt9URB4A@mail.gmail.com \
    --to=joel@aenertia.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=wmf@felter.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