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

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


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

chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_social/browse_social_twitter_infinite_scroll

Revision             Result                  N
chromium@485714      3.85476 +- 4.29629      21      good
chromium@485896      3.64895 +- 3.61253      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.infinite.scroll 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/8973748672349024528


For feedback, file a bug with component Speed>Bisection

The graphs have improved since the alerts.