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

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


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

chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win8-dual
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-scavenger_sum/browse_social/browse_social_twitter

Revision             Result                  N
chromium@488636      46.5478 +- 20.8913      21      good
chromium@488707      50.7366 +- 55.5626      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.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

This regression is with a large V8 changeset that includes landing 512K semi-space and other gc changes, which have many many regressions associated with them. I'll rather close this one and let's see how things look going forward.