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

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


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

chromium-rel-mac11
chromium-rel-win8-dual

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

=== 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_games/load_games_miniclip

Revision             Result                  N
chromium@514243      445.757 +- 2742.54      21      good
chromium@514318      473.026 +- 2641.22      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.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/8963468336746298640


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, and these look quite noisy.