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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/load_news/load_news_qq

Revision             Result                   N
chromium@490368      1.59935 +- 0.175364      21      good
chromium@490692      1.58433 +- 0.193341      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=load.news.qq system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Ref also moves.