Telemetry / Memory benchmark fix: Separate histograms for different tests.
commit82e85e2601d8c0074845d9e328b94eaca23230a1
authormarja@chromium.org <marja@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 14 Feb 2013 15:07:00 +0000 (14 15:07 +0000)
committermarja@chromium.org <marja@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 14 Feb 2013 15:07:00 +0000 (14 15:07 +0000)
tree193e18d819ecc372061e07ea02dcba73affeb104
parenta7e1dc03d78f4cc675c0e94a50ba40276cef7df0
Telemetry / Memory benchmark fix: Separate histograms for different tests.

We can't assume that all histograms are reset between test cases. We need to
remember start values for histograms before the test run, and subtract them from the
results.

memory_benchmark results before and after this CL are not comparable.

R=nduca
BUG=NONE
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/12221137

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@182467 0039d316-1c4b-4281-b951-d872f2087c98
tools/perf/perf_tools/histogram.py [new file with mode: 0644]
tools/perf/perf_tools/histogram_measurement.py [new file with mode: 0644]
tools/perf/perf_tools/histogram_unittest.py [new file with mode: 0644]
tools/perf/perf_tools/memory_benchmark.py