From b922101633f3ec5973b7c7de0956bbef09522e4f Mon Sep 17 00:00:00 2001 From: Evan Martin Date: Wed, 7 Dec 2011 12:30:59 -0800 Subject: performance testing note --- HACKING | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/HACKING b/HACKING index fc7712a..dcd5888 100644 --- a/HACKING +++ b/HACKING @@ -9,6 +9,15 @@ Test-driven development: Remember to build "all" before committing to verify the other source still works! +Testing performance impact of changes: + If you have a Chrome build handy, it's a good test case. + Otherwise, https://github.com/martine/ninja/downloads has a copy of + the Chrome build files (and depfiles). You can untar that, then run + "ninja chrome". I often do something like: + (for i in `seq 5`; do time -p ninja chrome) 2>&1 | grep real > old + (for i in `seq 5`; do time -p ninja-new chrome) 2>&1 | grep real > new + and then compare those two lists of timings either by eye or with R. + Coding guidelines: - Function name are camelcase. - Member methods are camelcase, expect for trivial getters which are -- cgit v0.12