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

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


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

android-nexus5
android-nexus6
chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@487019      8.95605 +- 2.21944      21      good
chromium@487021      8.77771 +- 1.93787      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=browse.social.twitter v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

MOstly recovered.