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

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


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

chromium-rel-win7-gpu-ati

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : JavaScript:duration_avg/browse_social/browse_social_twitter

Revision             Result                  N
chromium@510632      520.608 +- 20.3158      21      good
chromium@510673      520.516 +- 25.6704      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.twitter v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964567283921448160


For feedback, file a bug with component Speed>Bisection