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

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


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

chromium-rel-win7-gpu-ati

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : v1-large-deep-distribution/v1-large-deep-distribution

Revision             Result                  N
chromium@496635      29.3788 +- 2.7617       21      good
chromium@496956      28.9766 +- 1.48462      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection

Only on one testcase/bot, bisect can't repro.