From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Rich Brown <richb.hanover@gmail.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 09:17:30 +0200 [thread overview]
Message-ID: <20140912091730.2e762c93@redhat.com> (raw)
In-Reply-To: <A08116CF-B888-4C44-ABC6-2E6C80474C8B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
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.
"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: signature.asc --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2014-09-12 7:18 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 [this message]
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=20140912091730.2e762c93@redhat.com \
--to=jbrouer@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=joel@aenertia.net \
--cc=richb.hanover@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