From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (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 E1BA721F22D; Thu, 17 Apr 2014 10:49:14 -0700 (PDT) Received: by mail-wi0-f170.google.com with SMTP id bs8so204864wib.3 for ; Thu, 17 Apr 2014 10:49:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=NZ2cPcomXAuU7UhmBaMkN9zq/WBRGaGIaz2PBaISZYc=; b=mDTHmAeC5VlRrYQNqGxZyR4kwuK1K2PpdAF8OmoyXtwZK6ByuGz5BOPlxY0hV2BYue pC4VgFbXcHATrG/FUbwfeYWKsIdz4kLuAZIT4iATDqSLH7MRHvQE4G/mpNuzrSSex2ng VMFhirvrBpSNU/6yX/n7ltwMVWqOkGmStYuOAYuVrIBrmKetcPvepEwBbV0FVBLNbGvl RXHelT/FR9/GqG1sGKt1baS7SpmkvcjxvzNvGLYQomJalZqfTDW9VksyeTxpm3ETi+nA U7S/+UnXHVpykN1FUrmjMDlT4vOuRf0J5F0o5ddOEWKUoy4GfxZsbNKVyxEe6hRDv7Xd kOBQ== MIME-Version: 1.0 X-Received: by 10.194.9.8 with SMTP id v8mr3168291wja.53.1397756953071; Thu, 17 Apr 2014 10:49:13 -0700 (PDT) Received: by 10.216.177.10 with HTTP; Thu, 17 Apr 2014 10:49:13 -0700 (PDT) Date: Thu, 17 Apr 2014 10:49:13 -0700 Message-ID: From: Dave Taht To: "aqm@ietf.org" , bloat , "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] chrome web page benchmarker fixed 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: Thu, 17 Apr 2014 17:49:15 -0000 Getting a grip on real web page load time behavior in an age of sharded websites, dozens of dns lookups, javascript, and fairly random behavior in ad service= s and cdns against how a modern browsers behaves is very, very hard. it turns out if you run google-chrome --enable-benchmarking --enable-net-benchmarking (Mac users have to embed these options in their startup script - see http://www.chromium.org/developers/how-tos/run-chromium-with-flags ) enable developer options and install and run the chrome web page benchmarke= r, ( https://chrome.google.com/webstore/detail/page-benchmarker/channimfdomahe= kjcahlbpccbgaopjll?hl=3Den ) that it works (at least for me, on a brief test of the latest chrome, on li= nux. Can someone try windows and mac?) You can then feed in a list of urls to test against, and post process the resulting .csv file to your hearts content. We used to use this benchmark a lot while trying to characterise typical web behaviors under aqm and packet scheduling systems under load. Running it simultaneously with a rrul test or one of the simpler tcp upload or down= load tests in the rrul suite was often quite interesting. It turned out the doc has been wrong a while as to the name of the second command lnie option. I was gearing up mentally for having to look at the source.... http://code.google.com/p/chromium/issues/detail?id=3D338705 /me happy --=20 Dave T=C3=A4ht Heartbleed POC on wifi campus networks with EAP auth: http://www.eduroam.edu.au/advisory.html