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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_social/browse_social_tumblr_infinite_scroll

Revision             Result                     N
chromium@508090      0.255623 +- 0.013568       21      good
chromium@508171      0.255524 +- 0.0263947      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.social.tumblr.infinite.scroll 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/8965831450613029072


For feedback, file a bug with component Speed>Bisection

This has since recovered.