Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: "Wes Felter" <wmf@felter.org>,
	bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"Joel Wirāmu Pauling" <joel@aenertia.net>
Subject: Re: [Cerowrt-devel] [Bloat] Fixing bufferbloat: How about an open letter to the web benchmarkers?
Date: Fri, 12 Sep 2014 08:16:46 -0400	[thread overview]
Message-ID: <AFBCDABA-94AC-4B6C-9509-0C9C85FBD9F1@gmail.com> (raw)
In-Reply-To: <20140912091730.2e762c93@redhat.com>

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


On Sep 12, 2014, at 3:17 AM, Jesper Dangaard Brouer <jbrouer@redhat.com> wrote:

> On Thu, 11 Sep 2014 20:13:19 -0400
> Rich Brown <richb.hanover@gmail.com> wrote:
> 
>> I'll sign too. (And I like the 98th percentile measure for each
>> direction to give a single number that represents what's happening. It
>> could include ping loss rate, as well...)
> 
> I'll sign too.
> 
> The 98th percentile latency is of-cause nice, but we should remember to
> keep our request simple.

I did try a simple request and got a lukewarm response. You can see the gist of my correspondence with the test companies in https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-September/003517.html

Rich
 
> "Dear speedtest.net/speedof.me please add a latency test, that measures
> latency during the upload and download test-runs."
> 
> That will be the first baby step, don't make it too complicated for
> them, afterwards we can start explaining if we want min/max or 98th
> percentile.
> 
> They already have a ping facility, which the only run _before_ starting
> the test run.  Thus, they should be-able to easily adapt their existing
> "ping" code to measure during the test-runs... give then something they
> can easily do.
> 
> -- 
> Best regards,
>  Jesper Dangaard Brouer
>  MSc.CS, Sr. Network Kernel Developer at Red Hat
>  Author of http://www.iptv-analyzer.org
>  LinkedIn: http://www.linkedin.com/in/brouer


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2014-09-12 12:17 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
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 [this message]
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=AFBCDABA-94AC-4B6C-9509-0C9C85FBD9F1@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jbrouer@redhat.com \
    --cc=joel@aenertia.net \
    --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