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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer2
  Metric       : AngularJS-TodoMVC/Speedometer2

Revision             Result                  N
chromium@484085      3648.36 +- 1646.95      21      good
chromium@484123      3732.42 +- 1761.64      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=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection

The metric is just too flaky to run a meaningful bisect.