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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_avg/browse_news/browse_news_globo

Revision             Result                  N
chromium@503934      61.3012 +- 24.1246      21      good
chromium@503939      58.1414 +- 27.6616      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.globo v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection