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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=12db24ac26a36cb0e13dd836f82c2231d7caa2206dc7b4c3a90f39342668a108


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_tools/load_tools_dropbox

Revision             Result                     N
chromium@509543      0.370387 +- 0.0515091      21      good
chromium@509681      0.365521 +- 0.0332371      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.dropbox system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8965206298917698112


For feedback, file a bug with component Speed>Bisection

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

Kicked a bisect with a wider range: https://chromeperf.appspot.com/buildbucket_job_status/8964930953025482336

If it still can't reproduce it is likely an infrastructure change (no ref build running to check).

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_tools/load_tools_dropbox

Revision             Result                    N
chromium@509543      0.388643 +- 0.226543      21      good
chromium@509775      0.380753 +- 0.127519      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.dropbox system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964930953025482336


For feedback, file a bug with component Speed>Bisection

Going with what Patrick mentioned in comment#5.