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

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


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

android-nexus5X
android-nexus6
android-one
chromium-rel-mac11

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : speedometer
  Metric       : VanillaJS-TodoMVC/VanillaJS-TodoMVC

Revision             Result                  N
chromium@515942      2102.78 +- 193.751      21      good
chromium@515992      2120.72 +- 90.575       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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection