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" <[email protected] on behalf of [email protected]> 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 [email protected] https://lists.bufferbloat.net/listinfo/bloat _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
