Scott Ruthfield, Whitepages.com, a people search company with 2 bn searches per year, 500 requests/s at peak.
Initial analysis: 8s to return results, sub-second to actually get the data. What's the source of the slow-down? Possible candidates:
- Ads
- Microsoft Virtual Earth
- Content generated from the results
Toolset (Gomez networks) is not good enough because of poor sampling (20 samples per hours, compared to 1.3 MM requests) [should quantify error margin here, presumably high assuming a normal distribution]
Introducting Jiffy. Objectives: measure anything, with little impact on page performance. Architecture starts with a jiffy.js that generates logs, then loaded into a DB and rolled up.
Basic tenet: mark and measure. One mark, multiple measures.
Miscellaneous features: immediate or batch submits (to not overload measurement system), default browser event measurements (onload, etc.)
Bill Scott @netflix put together a firebug plug-in to capture client-side data.
Source:
code.whitepages.com
