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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Dan Elphick
  Commit : 67fac36a35318d03fe141887898821e42dfaecb4
  Date   : Fri Jul 07 08:57:32 2017
  Subject: Increase priority of compositor TQ in NONE Usecase

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc
  Metric       : cpu_time_percentage_avg/720p_call_45s
  Change       : 1.66% | 0.547056693291 -> 0.55615019274

Revision             Result                      N
chromium@484862      0.547057 +- 0.0160508       14      good
chromium@484863      0.562295 +- 0.0254528       6       bad       <--
chromium@484864      0.556981 +- 0.0119326       6       bad
chromium@484866      0.55529 +- 0.0163798        9       bad
chromium@484869      0.554997 +- 0.00959945      6       bad
chromium@484875      0.56398 +- 0.0141018        6       bad
chromium@484887      0.554339 +- 0.0114705       6       bad
chromium@484912      0.55615 +- 0.0175256        9       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=720p.call.45s webrtc

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

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


For feedback, file a bug with component Speed>Bisection