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

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


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

chromium-rel-win8-dual
linux-release

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_accessibility_shopping/load_accessibility_shopping_amazon

Revision             Result                  N
chromium@511986      230.776 +- 1612.25      21      good
chromium@512100      241.446 +- 1472.14      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.accessibility.shopping.amazon 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/8964184506858065856


For feedback, file a bug with component Speed>Bisection

Bisect can't repro.