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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_sum/browse_social/browse_social_twitter

Revision             Result                  N
chromium@498971      6.07316 +- 5.04923      19      good
chromium@499106      6.45284 +- 3.85783      19      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.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/8969399488524570416


For feedback, file a bug with component Speed>Bisection

Too much noise