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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_accessibility_tech/browse_accessibility_tech_codesearch

Revision             Result                    N
chromium@510764      0.193544 +- 0.135828      21      good
chromium@510824      0.19162 +- 0.172266       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 --story-filter=browse.accessibility.tech.codesearch 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/8964186636947507440


For feedback, file a bug with component Speed>Bisection

This came back down.