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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzoHmpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjo7O8QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjqaMowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjuiE4woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjp_QpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjpC4qgsM


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

android-nexus5X
android-nexus6
android-webview-nexus5X

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

=== Auto-CCing suspected CL author altimin@chromium.org ===

Hi altimin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Alexander Timin
  Commit : b79c8f273a4610054eebebd959a2b1177bb4e431
  Date   : Mon Jun 19 12:09:32 2017
  Subject: [scheduler] Make PostedMessage and UserInteraction tasks unthrottled.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : cpu_time_percentage_avg/browse_social/browse_social_instagram
  Change       : 5.97% | 0.560326560288 -> 0.593790507806

Revision             Result                      N
chromium@480379      0.560327 +- 0.0042422       6      good
chromium@480398      0.558545 +- 0.00716463      6      good
chromium@480407      0.562043 +- 0.00827643      6      good
chromium@480408      0.592406 +- 0.00839544      6      bad       <--
chromium@480409      0.591955 +- 0.00483979      6      bad
chromium@480410      0.593758 +- 0.00315686      6      bad
chromium@480412      0.594365 +- 0.00980155      6      bad
chromium@480416      0.594784 +- 0.00870083      6      bad
chromium@480453      0.592177 +- 0.00563516      6      bad
chromium@480527      0.593791 +- 0.00630353      6      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.instagram system_health.common_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976142411390215952

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5889811224723456


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

These regressions are derived from the fact that these tests run faster, so average cpu usage per second is higher (but overall cpu usage has decreased).