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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAq6PktwoM


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

android-nexus6

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

Hi sievers@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Revert "Revert of android: Remove custom browser compositor scheduling logic (patchset #6 id:100001 of https://codereview.chromium.org/1513933003/ )"
Author  : sievers
Commit description:
  
AKA Reland of https://codereview.chromium.org/1513933003/
> android: Remove custom browser compositor scheduling logic
>
> Use cc scheduler instead without a deadline.
> This is mostly obsolete now that Surfaces allow independent updates
> between renderer and browser.
>
> BUG= 455894 
> Committed: https://crrev.com/7f045e4f2e9f7142c79e2eeb30b70716a1ea8f0b
> Cr-Commit-Position: refs/heads/master@{#365861}
>
(Flakiness is fixed with https://codereview.chromium.org/1560533004/)

This reverts commit 1b0f7d5ea39348411bdd0997dde85eecc7fdb19f.

TBR=brianderson@chromium.org

Review URL: https://codereview.chromium.org/1558183003

Cr-Commit-Position: refs/heads/master@{#367710}
Commit  : 48c068db031cb19d0bbfcb7ee697cdd94837105c
Date    : Wed Jan 06 00:15:50 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@367700         11.92       1.950467    5           good
chromium@367706         9.7816      2.741242    5           good
chromium@367709         13.6604     4.280592    5           good
chromium@367710         32.3228     6.529334    5           bad         <-
chromium@367711         31.4128     5.221155    5           bad
chromium@367712         32.5518     3.829459    5           bad
chromium@367723         28.5558     7.261079    5           bad
chromium@367746         30.651      8.031925    5           bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 600375

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.key_mobile_sites_smooth
Test Metric: first_gesture_scroll_update_latency/http___www.cnn.com_2012_10_03_politics_michelle-obama-debate_index.html
Relative Change: 157.14%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2088
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016305108149224336


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=600375

| 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 Tests>AutoBisect.  Thank you!

> first_gesture_scroll_update_latency

Probably same as 591725 then.

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Revert "Revert of android: Remove custom browser compositor scheduling logic (patchset #6 id:100001 of https://codereview.chromium.org/1513933003/ )"
Author  : sievers
Commit description:
  
AKA Reland of https://codereview.chromium.org/1513933003/
> android: Remove custom browser compositor scheduling logic
>
> Use cc scheduler instead without a deadline.
> This is mostly obsolete now that Surfaces allow independent updates
> between renderer and browser.
>
> BUG= 455894 
> Committed: https://crrev.com/7f045e4f2e9f7142c79e2eeb30b70716a1ea8f0b
> Cr-Commit-Position: refs/heads/master@{#365861}
>
(Flakiness is fixed with https://codereview.chromium.org/1560533004/)

This reverts commit 1b0f7d5ea39348411bdd0997dde85eecc7fdb19f.

TBR=brianderson@chromium.org

Review URL: https://codereview.chromium.org/1558183003

Cr-Commit-Position: refs/heads/master@{#367710}
Commit  : 48c068db031cb19d0bbfcb7ee697cdd94837105c
Date    : Wed Jan 06 00:15:50 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@367700         10.0088     1.997433    5           good
chromium@367706         10.0174     0.528081    5           good
chromium@367709         11.9162     2.238023    5           good
chromium@367710         35.8044     1.579386    5           bad         <-
chromium@367711         34.8286     1.946261    5           bad
chromium@367712         33.3344     5.066283    5           bad
chromium@367723         37.0206     1.426322    5           bad
chromium@367746         36.5312     1.781688    5           bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 600375

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.key_mobile_sites_smooth
Test Metric: first_gesture_scroll_update_latency/http___www.cnn.com_2012_10_03_politics_michelle-obama-debate_index.html
Relative Change: 264.99%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2087
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016305118027440192


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=600375

| 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 Tests>AutoBisect.  Thank you!