From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 9A8E521F5D0; Fri, 25 Jul 2014 08:46:36 -0700 (PDT) Received: by mail-qa0-f49.google.com with SMTP id dc16so4681479qab.22 for ; Fri, 25 Jul 2014 08:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=OBuP0+4U1j4ceXj5sbWsLxGZBcFIjLWoI2cYu06mt+Y=; b=zDnbFwajPPONEvm7S2sFfBSwn6LrTVzz0+kx7oBs6Y5g7oKoWdBrRg07J8Ir1UeklU vNlBjQdwmjMxHwZldrrUgcydHjDWD+zxPF6am+qUKcouuF8pzK9h7JcKeZBULuC1TPQx yj4CLCoSDeStCVc+vhAYnLoI0xg3etyLeBTi4JFh1OIgVYRMs6Ir1v+gJPQJ2DWgnet4 1mG4L4ox84llAm4QrPHTPO/7E9IgQcEc7LKxRIpPX27oGKSlOhqVNYEIN7rBDJof/7Jq IZthvDOwe6T53c8A4/+HlCsyH3wBfmLCVzQvpSoEPpOuNjFogKY4j/WHN1tr1MGuNKVk J5XA== X-Received: by 10.224.47.8 with SMTP id l8mr29187612qaf.30.1406303195377; Fri, 25 Jul 2014 08:46:35 -0700 (PDT) Received: from richs-mbp-5319.home.lan (pool-72-95-118-52.phlapa.east.myfairpoint.net. [72.95.118.52]) by mx.google.com with ESMTPSA id u36sm11662655qge.43.2014.07.25.08.46.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Jul 2014 08:46:34 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_85332351-916D-4F5B-92B5-45687EE8479E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Rich Brown In-Reply-To: Date: Fri, 25 Jul 2014 11:46:27 -0400 Message-Id: References: <03292B76-5273-4912-BB18-90E95C16A9F5@pnsol.com> To: Neil Davies X-Mailer: Apple Mail (2.1878.6) Cc: cerowrt-devel , bloat Subject: Re: [Cerowrt-devel] [Bloat] Check out www.speedof.me - no Flash X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2014 15:46:37 -0000 --Apple-Mail=_85332351-916D-4F5B-92B5-45687EE8479E Content-Type: multipart/alternative; boundary="Apple-Mail=_9E651F6D-9FCC-40C5-B3F9-2CAB1AB21FE4" --Apple-Mail=_9E651F6D-9FCC-40C5-B3F9-2CAB1AB21FE4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi Neil, > I have a deep worry over this style of single point measurement - and = hence speed - as an appropriate measure. We know, and have evidence, = that throughput/utilisation is not a good proxy for the network = delivering suitable quality of experience. We work with organisation = (Telco=92s, large system integrators etc) where we spend a lot of time = having to =93undo=94 the consequences of =93maximising speed=94. Just = like there is more to life than work, there is more to QoE than speed. I completely agree with this: those of us who have spent the time to = ponder the physics of the problem have come to understand it in its full = glory (and complexity). We know that a single number ain't the answer. =20 But one of my other goals is to increase the awareness of the = bufferbloat problem. People *do* use these speed test services, despite = their inaccuracy. If those sites could include some form of measurement = about the latency (and its change) under load, it makes it easier to = describe the problem to others. The long-term solution is, of course, to get router vendors to realize = there's a problem and then respond to market pressures to fix it. I = gained a lot of insight from http://apenwarr.ca/log/?m=3D201407#11 - it = has a description of the difficult economic justification for selling a = "good router". But where that author was trying to start a company, = we're in a different position.=20 Good latency info in a popular speed test website elevates its = importance to the general public. It moves you out of the "nutcase" = category ("What's this bufferbloat stuff this guy's talking about?"), = into a concerned customer who's offering a useful observation. And it = gives credibility when you bug providers. Examples: - A lot of people reflexively check speedtest.net when they check into a = hotel, and then post/tweet the results. If the results include min/max = latency, then they can begin to comment to the hotel (where they may = even have been charged for the service) when things aren't good.=20 - I frequently ride a bus to Boston that offers free wifi. I already = know they're badly bloated (>20 seconds(!)). With a tool like this, it's = easier to begin a conversation with the operations people that lets them = put pressure on their own router vendor.=20 - Home and commercial users can use these values to tell their ISPs that = there's a problem, and the expense of fielding those support calls = provides some incentive to address the problem. - Heaven forbid one vendor/provider snatch up the idea and tout it as a = competitive advantage... :-) We've shown that there is a straightforward fix to the problem. With = increased awareness from their customers, I hold out hope that we can = begin to change the world. Best, Rich PS Thanks to Sebastian for the comments, and Martin for those links. --Apple-Mail=_9E651F6D-9FCC-40C5-B3F9-2CAB1AB21FE4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hi = Neil,

I have a deep worry over this style of = single point measurement - and hence speed - as an appropriate measure. = We know, and have evidence, that throughput/utilisation is not a good = proxy for the network delivering suitable quality of experience. We work = with organisation (Telco=92s, large system integrators etc) where we = spend a lot of time having to =93undo=94 the consequences of =93maximising= speed=94. Just like there is more to life than work, there is more to = QoE than speed.

I completely = agree with this: those of us who have spent the time to ponder the = physics of the problem have come to understand it in its full glory (and = complexity). We know that a single number ain't the = answer.
 
But one of my other goals is to = increase the awareness of the bufferbloat problem. People *do* use these = speed test services, despite their inaccuracy. If those sites could = include some form of measurement about the latency (and its change) = under load, it makes it easier to describe the problem to = others.

The long-term solution is, of course, = to get router vendors to realize there's a problem and then respond to = market pressures to fix it. I gained a lot of insight from http://apenwarr.ca/log/?m=3D= 201407#11 - it has a description of the difficult economic = justification for selling a "good router". But where that author was = trying to start a company, we're in a different = position. 

Good latency info in a popular = speed test website elevates its importance to the general public. It = moves you out of the "nutcase" category ("What's this bufferbloat stuff = this guy's talking about?"), into a concerned customer who's offering a = useful observation. And it gives credibility when you bug providers. = Examples:

- A lot of people reflexively check = speedtest.net when they check into = a hotel, and then post/tweet the results. If the results include min/max = latency, then they can begin to comment to the hotel (where they may = even have been charged for the service) when things aren't = good. 
- I frequently ride a bus to Boston that offers = free wifi. I already know they're badly bloated (>20 seconds(!)). = With a tool like this, it's easier to begin a conversation with the = operations people that lets them put pressure on their own router = vendor. 
- Home and commercial users can use these values = to tell their ISPs that there's a problem, and the expense of fielding = those support calls provides some incentive to address the = problem.
- Heaven forbid one vendor/provider snatch up the = idea and tout it as a competitive advantage... = :-)

We've shown that there is a straightforward = fix to the problem. With increased awareness from their customers, I = hold out hope that we can begin to change the = world.

</utopian = rant>

Best,

Rich

PS Thanks to Sebastian for the comments, and Martin = for those links.
= --Apple-Mail=_9E651F6D-9FCC-40C5-B3F9-2CAB1AB21FE4-- --Apple-Mail=_85332351-916D-4F5B-92B5-45687EE8479E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJT0nvYAAoJEH4agC/0z73/Gg0H/0tGysbszcbSOLBe/NrZi83g 4kF0gcoQMrI/zkgL8TSnSXPGyBQB7Y8qHhs87o19kJyA/rCOLtzoFU1Y7IDVeYkh /Xx+AYPoucTxOhdKcq3hnQR3TqKF8pBuDPIdQvK0Dm399UdZxanlCyMivjzjGMMT lZkriRn1iEcdlGD+AKMBmqV2tUI2N/QquukJoyPV2BjfmRmUCYjZLWHHCRopo6Oy qV8NdWWrlxwMIDN9YPLAj9h+FRsDkK+1GAwmiBI5AURFEBxxGaNW1yPTgqJcclmq Yoy7Z3IqRZ5beJCVkSoiim1FHXdumYYe8boj8AHWOOQCNYs4vBBBGolMyh5K+2o= =HZdP -----END PGP SIGNATURE----- --Apple-Mail=_85332351-916D-4F5B-92B5-45687EE8479E--