From: Stephen Hemminger <stephen@networkplumber.org>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Open Source Speed Test (was fast.com - Netflix's speed monitoring)
Date: Wed, 24 Aug 2016 09:08:47 -0700 [thread overview]
Message-ID: <20160824090847.4e77ce8f@xeon-e3> (raw)
In-Reply-To: <0B9BB2F0-611E-4388-8784-0AC71556AB4B@cable.comcast.com>
On Tue, 23 Aug 2016 18:42:07 +0000
"Livingood, Jason" <Jason_Livingood@comcast.com> wrote:
> FWIW, we at Comcast just announced public beta of a new soon-to-be-open-source web-based speed test (see http://labs.comcast.com/beta-testing-a-new-open-source-speed-test). We plan to have a hackathon at Princeton in early November (see https://citp.princeton.edu/event/speedtest-hackathon/). One of the items in the backlog and suggested for one of the hackathon teams to work on is a buffer bloat test.
>
> If anyone here is interested in participating, ping me off-list (we have a limited number of spots available).
>
> Thanks!
> Jason
>
Why doesn't the test measure bufferbloat like FLENT or dslreports test?
next prev parent reply other threads:[~2016-08-24 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:42 Livingood, Jason
2016-08-24 16:08 ` Stephen Hemminger [this message]
2016-08-24 17:28 ` Livingood, Jason
2016-08-26 23:13 ` Kathleen Nichols
2016-08-26 23:20 ` David Lang
2016-08-26 23:37 ` Kathleen Nichols
2016-08-27 1:06 ` David Lang
2016-08-27 5:02 ` grenville armitage
2016-08-27 12:16 ` Jonathan Morton
2016-08-27 0:20 ` Benjamin Cronce
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=20160824090847.4e77ce8f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
/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