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

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


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

chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@493971      1.32981 +- 1.78751      21      good
chromium@493983      1.50252 +- 2.26912      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/8971279071091631104


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@493971      1.39238 +- 2.17735      21      good
chromium@493983      1.461 +- 2.37463        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/8971113508877621808


For feedback, file a bug with component Speed>Bisection

The benchmark has been disabled, need to figure out why.