From: dpreed@reed.com
To: "Jonathan Morton" <chromatix99@gmail.com>
Cc: "Wes Felter" <wmf@felter.org>,
"Joel Wirāmu Pauling" <joel@aenertia.net>,
"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: Thu, 11 Sep 2014 21:24:27 -0400 (EDT) [thread overview]
Message-ID: <1410485067.393724599@apps.rackspace.com> (raw)
In-Reply-To: <45F70DEB-F0FE-45EA-8D27-EEF7C523476B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
The speedof.me API probably can be used directly as the measurement of download and upload - you can create a competing download or upload in Javascript using a WebWorker talking to another server that supports the websocket API to force buffer overflow. (sort of poor man's RRUL).
The speedof.me API would give you the measured performance, while the other path would just be aan easier to code test load to a source/sink.
Not sure that would help, but for a prototype it's not bad.
On Thursday, September 11, 2014 8:42pm, "Jonathan Morton" <chromatix99@gmail.com> said:
>
> On 12 Sep, 2014, at 3:35 am, dpreed@reed.com wrote:
>
> > Among friends of mine, we can publicize this widely. But those friends
> probably would like to see how the measurement would work.
>
> Could we make use of the existing test servers (running netperf) for that
> demonstration? How hard is the protocol to fake in Javascript?
>
> Or would a netperf-wrapper demonstration suffice? We've already got that, but
> we'd need to extract the single-figures-of-merit from the data.
>
> I wonder if the speedof.me API can already be tricked into doing the right thing?
>
> - Jonathan Morton
>
>
[-- Attachment #2: Type: text/html, Size: 2166 bytes --]
next prev parent reply other threads:[~2014-09-12 1:24 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 [this message]
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
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=1410485067.393724599@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.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