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

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


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

health-plan-clankium-phone

Maria or Ben, is this a genuine issue?

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

We will need to see what the bisect shows to know.

 Issue 844633  has been merged into this issue.

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

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : start_with_url.warm.startup_pages
  Metric       : messageloop_start_time/messageloop_start_time
  Change       : 0.55% | 1232.51133333 -> 1225.71107143

Revision                       Result                  N
android-chrome@ce55fd46c1      1232.51 +- 42.8294      21      good
android-chrome@8f25dd139d      1225.71 +- 11.2993      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=5 --also-run-disabled-tests start_with_url.warm.startup_pages

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

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


For feedback, file a bug with component Speed>Bisection

Looking at the graphs it seems like slowing down by 30ms after a month of being faster. See: https://chromeperf.appspot.com/report?sid=08274e47fd44005eec8591e8d431c602c86428d18c852c367a76ed6fd0487f14&start_rev=1523753204&end_rev=1526844862

A startup regression this small in magnitude is probably not bisectable. Not sure what to do.