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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_search/load_search_yahoo

Revision             Result                      N
chromium@518614      0.0485175 +- 0.014028       21      good
chromium@518676      0.0475706 +- 0.0132902      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=load.search.yahoo 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/8962044325865213280


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, and this came back down.