All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=684474

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsPj7oAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0POEtAoM


Bot(s) for this bug's original alert(s):

chromium-rel-mac11

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989590825573576272

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/load_tools/load_tools_maps

Revision             Result                  N
chromium@445300      355.081 +- 28.6167      21      good
chromium@445301      353.734 +- 23.3606      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.maps system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989590825573576272

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5822622840913920


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

was a temporary spike