Looks relevant to FxA perf testing. Begin forwarded message:
> From: Mark Mayo <[email protected]> > Subject: Fwd: Marketplace Performance Tests > Date: June 24, 2014 at 10:22:29 PM PDT > To: "[email protected]" <[email protected]> > > note sure how many of our folks are on the webdev mailing list, but this one > looked 'relevant to our interests'. > > -m > > ---------- Forwarded message ---------- > From: Christopher Van <[email protected]> > Date: Tue, Jun 24, 2014 at 10:14 PM > Subject: Marketplace Performance Tests > To: [email protected], WebDev <[email protected]> > > > I'm trying out this service called SpeedCurve. It uses WebPagetest behind the > scenes but with an actually decent UI. > > It runs 108 "synthetic" tests across Amazon servers to do perf tests across > all the major browsers. (A good read: > http://speedcurve.uservoice.com/knowledgebase/articles/355134-synthetic-vs-real-user-monitoring-rum) > > Here are stats comparing Marketplace prod vs. Google Play vs. Google Chrome > Web Store: > > http://speedcurve.com/share/bae1o9hxq2nvetwzno8o6996zr4mc2/ > > Yeah, that's right - we are pretty darn fast even by Google standards. > > And Marketplace prod vs. stage vs. dev: > > http://speedcurve.com/share/dfbj4g5ltp43k30xt17fj5zvm6lllj/ > > Keep an eye on these pages as they get updated daily and watch how fast we > get. > > I had written my own perf measurement tool (called phantomHAR), but this > thing seems to work and looks great (although it's unfortunately not open > source yet). > > phantomHAR fetches a URL (based on a manual POST or GitHub webhook), > generates a HAR (the JSON that can render waterfall graphs you see in the > Network tab of your favourite browser's Developer Tools), tallies up all the > response sizes and times, and then the front-end renders graphs of the > response sizes, response times, and number of requests for each type of > request (e.g., HTML document/JS/CSS/inline image/CSS image/etc.). I use a > fantastic tool called chromeHAR <https://github.com/ericduran/chromeHAR> to > render the HARs (meaning, when you click on a particular date, you can see > the waterfall graph of all the network requests made with the > request/response headers, response sizes, tabs for each request type, etc. - > just like in your browser's devtools). > > This is what an early version of what phantomHAR looks like: > > http://people.mozilla.org/~cwiemeersch/phantomhar/ > > I'm going to continue work on phantomHAR because it gives me the information > I want — perf metrics after I push code to our staging/dev servers. I like > that because when I remove 300 lines of JS, remove a webfont, or upgrade > jQuery, I want to immediately see how much faster/slower I affected the site > and how many bytes I saved/wasted with that change. Keeping an audit trail of > the network requests is imperative if you're going to ever know if you're > getting faster or slower. Things like NewRelic help this on the server, but > there really aren't any good tools that help developers diff the network > requests each time new code is pushed to their servers. > > There's a similar tool that also uses PhantomJS to do perf profiling. It's > called phantomas <https://github.com/macbre/phantomas> and it does a heck of > a lot, and I've been contributing to it. There's a grunt plugin called > grunt-phantomas <https://github.com/stefanjudis/grunt-phantomas> that can > generate many, many pretty graphs from the resulting JSON (see > http://cvan.io/marketplace-perfboard/prod/ for examples). Besides showing too > much information, its HAR generator > <https://github.com/macbre/phantomas/blob/master/modules/har/har.js> > generates incorrect filesizes because of an age-old PhantomJS bug > <https://github.com/ariya/phantomjs/issues/10156> > <https://github.com/ariya/phantomjs/issues/10158>. YSlow, netsniff.js, and > many other PhantomJS-based scripts are also inaccurate. I've worked around > these issues with phantomHAR (fastHAR-api) until the fix > <https://github.com/ariya/phantomjs/pull/11484> gets upstreamed to phantomJS. > > Anyway, if people are interested in contributing to phantomHAR, holler at me > because I could use some help with it (it's all NodeJS/JS). I'll be > consolidating the repos but for now there are three of them: > > https://github.com/cvan/phantomHAR > https://github.com/cvan/fastHAR-api > https://github.com/cvan/fastHAR > > When officially launched, phantomHAR live at arewefast.com/arewefast.org. > > Anyway, keep an eye on the SpeedCurve URLs. And reach out to me if you're > interesting in helping me with front-end perf monitoring. >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
