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

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


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

android-nexus5
android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_tools/browse_tools_maps

Revision             Result                  N
chromium@514420      4431.76 +- 2940.82      21      good
chromium@514451      4468.74 +- 2499.28      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.tools.maps 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/8962786529172335776


For feedback, file a bug with component Speed>Bisection