From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Open Source Speed Test (was fast.com - Netflix's speed monitoring)
Date: Tue, 23 Aug 2016 18:42:07 +0000 [thread overview]
Message-ID: <0B9BB2F0-611E-4388-8784-0AC71556AB4B@cable.comcast.com> (raw)
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
On 8/17/16, 7:33 AM, "Bloat on behalf of Rich Brown" <bloat-bounces@lists.bufferbloat.net on behalf of richb.hanover@gmail.com> wrote:
I just saw Netflix's Fast.com site. They (may) suffer from non-neutral treatment by various carriers, so they set up their own testing suite so that their customers can see if Netflix servers are getting full treatment.
Netflix make interesting choices in the design of the test. They only measure download speed (since that's their customer's major beef). It's a really attractive page, and it's pretty clear what they're doing.
This blog posting tells how they designed it and some of the challenges. http://techblog.netflix.com/2016/08/building-fastcom.html
Cheers!
Rich
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next reply other threads:[~2016-08-23 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:42 Livingood, Jason [this message]
2016-08-24 16:08 ` Stephen Hemminger
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=0B9BB2F0-611E-4388-8784-0AC71556AB4B@cable.comcast.com \
--to=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