Building Performance Testing into the Development Process

Barrett SmithTechnical Program Lead

d.o: Barretttwitter: ba66e77

Assumptions

performance is importantperformance can not be an afterthought of development

I assume you have accepted that…

So how do we build performance testing into our development process

Step 1: Operationalize.That.Messdefine what performance you care about

page load timesapi submissions per secondtime to complete a given action

come to agreement on how to measure itcome to agreement on acceptable values

Step 2: Group Hug with Content Teamhow much bling are they willing to give up for performancewhat ownership are they willing to take for optimizing content

Step 3: Add to your development flowDevelopment and architecture

build it right from the startwhen in doubt, see http://www.whatwouldmarksonnabaumdo.com/

Code reviewinclude explicit checks for anti-patterns

Step 3b: Stakeholder reviewStakeholder review

strawman pages with representative content

Step 3c: Post-Launch monitoringPost-Launch monitoring

regular, historic tracking of performance

The Tools: Google AnalyticsThe Good

ubiquitousRUM metricsgeographic detail

The BadRUM metricsdelay in reporting

The Tools: Google Page SpeedThe Good

provides improvement suggestionsfreeeasy to use

The Badsynthetic requestno actual page time metric

The Tools: Trace View or New RelicThe Good

RUM capabilitiesserver detail ala xhprof

The Badcostrequires server components

The Tools: Browser consoleThe Good

access to local environmentsThe Bad

limited detail

The Tools: webpagetest.orgThe Good

freerobust feature setdetailed reportingvideos!

The Badno access to private siteson demand only

The Tools: Speed CurveThe Good

historic reportinggood detail of information

The Badexplicit page checkingnot free

Demo

Thank you