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

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


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

chromium-rel-mac11
chromium-rel-mac12
chromium-rel-win7-dual

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

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

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

Revision             Result                  N
chromium@511013      3.61248 +- 14.8566      21      good
chromium@511067      2.36995 +- 5.32854      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/8963949163880671152


For feedback, file a bug with component Speed>Bisection