On 14/05/15 13:11, Rich Brown wrote:
> Folks,
>
> Today is the third anniversary of the announcement of a testable fq_codel (see https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-May/002984.html et. seq.)
Happy Birthday! :-)
> - Speaking of which, the new DSLReports Speed Test has recently stirred things up. Not only do we have an attractive tool that we can recommend to friends, but people are getting a little hot under the collar when they see the crummy performance of the router that they just paid dearly for. See, for example, http://www.dslreports.com/forum/r30051856-Connectivity-Buffer-Bloat
>
>

Not just dslreports.  Thinkbroadband (quite popular in the UK) have been 
working on a new HTML5 based 'speed/latency' test (they've been 
collecting data for a few months) 
http://www.thinkbroadband.com/speedtest.html

It looks like it's still in progress and only gives a 'bufferbloat 
rating' rathing than DSLReport's pretty graphs, BUT it is adding to the 
tide of bufferbloat awareness which can only be a good thing.

My awareness and interest has certainly been piqued over the past few 
months.  Dave & Jim's explanations of bufferbloat have been avid 
reading/viewing here, as has the increasing alarm at the poor^H^H^H^H 
non-existent support of standard CPE routing devices (I now won't touch 
anything older than linux 3.0 based)  'Friends don't let friends run 
factory firmware' (especially parents) has been the motivation for 
switching to OpenWrt as well as bufferbloat improvements (though I'm 
also concerned by coding monocultures) Most things have stretched my 
circa 1990 unix sys admin skills (used to sysadmin before another path 
took hold) but picking up little tidbits of info from this list and 
others, I hope to be able to contribute in the near future.

Sincerest thanks to (in no particular order) Jim, Dave, Toke, Alan & all 
the crew here for working on the bufferbloat problem.

Kevin