From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pacdcmhout01.cable.comcast.com (PACDCMHOUT01.cable.comcast.com [68.87.31.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 91A7221F2E2 for ; Mon, 30 Mar 2015 09:20:55 -0700 (PDT) X-AuditID: 44571fa7-f79336d000000ff4-20-551977e55367 Received: from pacdcexhub04.cable.comcast.com (dlpemail-wc-5p.sys.comcast.net [24.40.13.176]) by pacdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 13.D6.04084.5E779155; Mon, 30 Mar 2015 12:20:53 -0400 (EDT) Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.14]) by pacdcexhub04.cable.comcast.com ([fe80::1532:d330:f9a5:c8a1%18]) with mapi id 14.03.0181.006; Mon, 30 Mar 2015 12:20:48 -0400 From: "Livingood, Jason" To: Dave Taht Thread-Topic: [Bloat] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Thread-Index: AQHQakbyzXDeMeZaBEyomNm2kaE0jJ003rqAgAByWYCAAAYXgIAAAMmAgAAJjoD//9TnMg== Date: Mon, 30 Mar 2015 16:20:03 +0000 Message-ID: <79A15A65-80E8-4117-A19C-88F8FF2BE44E@cable.comcast.com> References: <20150316203532.05BD21E2@taggart.lackof.org> <123130.1426635142@turing-police.cc.vt.edu> <15A0911A-E3B7-440A-A26B-C5E1489EA98B@viagenie.ca> <1426773234.362612992@apps.rackspace.com> <1426796961.194223197@apps.rackspace.com> <5FD20B4A-A7E8-48C0-89F9-E2EB86DED8A6@gmail.com> <755FC1BE-141C-42FD-B3E3-564488982665@gmail.com> <95B0F8DA-7650-4064-BEE6-F0CDF936D33A@gmail.com> , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Forward X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrIIsWRmVeSWpSXmKPExsUiocG7QfdpuWSowf2nxhb9v+6zWizc9oPR YsXXPiaL+cv1HVg8ds66y+6x/eIZJo9Pe54wBTBHcdmkpOZklqUW6dslcGX8ujuFsWAbb8Wi y91sDYwvuLoYOTkkBEwkVkztZ4ewxSQu3FvP1sXIxSEkcJNRYt2pLlaQhJDAQUaJ09OSQWw2 ARuJ6duOMoPYIgLKElPun2AHaWAWWMQo0f30E1hCWCBR4uXOA2wQRUkSRw7fZ4WwwySat89l BLFZBFQlrmxZCFbDK+AiMW3Sd1aIzd0cEjs+bgc7iVMgUKLz7yOwBkag876fWsMEYjMLiEvc ejKfCeJsAYkle84zQ9iiEi8f/2OFqNGRWLD7ExuErS2xbOFrZohlghInZz5hgagXlzh8ZAfr BEaxWUjGzkLSPgtJ+ywk7QsYWVYxyhUkJqck52bkl5YYGOolJyblpOol5+cmJxaXgOhNjMCI cwmXX76D8d4Lp0OMAhyMSjy8v5IkQ4VYE8uKK3MPMUpwMCuJ8EaXAIV4UxIrq1KL8uOLSnNS iw8xSnOwKInzFuQDpQTSE0tSs1NTC1KLYLJMHJxSDYzCH+UYX39XunbtJC+vv2yMBKvPIcFG zfhL2XstP6yt8iuLs07VmDM35KbSMq+9XLcD1wnouCY7ZQuuZfzEx9UuVcydaHKqVfpFVs25 1dz7Cw2299xbmflwx41rR4487PvdkRabwM2bYKCpITC5dsu5q/Ixk1YGe/j0Fq+Qv62t2ZDJ 9u/VYyWW4oxEQy3mouJEAMThCy+0AgAA Cc: Jonathan Morton , "dpreed@reed.com" , bloat Subject: Re: [Bloat] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 16:21:24 -0000 Could be via a browser plugin? Regards, Jason=20 Jason Livingood Comcast - Internet Services > On Mar 30, 2015, at 11:55, Dave Taht wrote: >=20 > I think the most effective thing would be to add bufferbloat testing > infrastructure to the web browsers themselves. There are already > plenty of tools for measuring web performance (whyslow for firefox, > the successor to chrome web page benchmarker) more or less built in... > measuring actual network performance under load is not much of a > reach. >=20 > The issues this would resolve are: >=20 > 1) speed - the test(s) could use native apis within the browser and > thus achieve higher rates of speed than is possible with javascript > (and monitor cpu usage) > 2) we could rigorously define the tests to have similar features to > netperf-wrapper > 3) we could get much better tcp statistics as in with TCP_INFO > 4) output formats could still be json as we do today, but plotted better > 5) ? >=20 > Problems are: >=20 > 0) Convincing users to use (and believe) them > 1) Suitable server targets for the tests themselves > 2) Although the browsers are basically in a nearly quarterly update > cycle, it would still take time for the tests to be widely available > even if they were ready today > 3) Convincing the browser makers that they could use such tests > 4) Writing the tests (in C and C++) > 5) The outcry at speedtest, et al, for obsoleting their tools > (think microsoft vs "stacker") > 6) Bloating up the browsers still further > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >=20