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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_social/browse_social_facebook

Revision             Result                   N
chromium@486073      1.35686 +- 0.158905      21      good
chromium@487676      1.3807 +- 0.135162       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.social.facebook 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/8973104507675750640


For feedback, file a bug with component Speed>Bisection

Ref moved at same time.