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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_games/load_games_miniclip

Revision             Result                  N
chromium@510723      165.669 +- 1674.75      21      good
chromium@510764      87.3088 +- 205.403      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.games.miniclip 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/8964771358018843936


For feedback, file a bug with component Speed>Bisection

This recovered.