scheduler: Optimize for TouchStart responsiveness by modeling what the user is doing.

scheduler: Optimize for TouchStart responsiveness by modeling what the user is doing.

We have come to realize that TouchStart responsiveness is really critical for a
good user experience. This patch introduces a (initially very simple) system
for modeling what the user is doing and predicting when they are likely to
initiate a new gesture (taps are ignored).  We order task priority accordingly.

In addition we extend the estimation of task cost to loading tasks
which are often a significant source of jank.

Load tasks can be very long (easily up to 1000ms). There is
no good way to cooperatively schedule such a task but the
least worst user experience seems to be if we get them out
of the way as fast as possible.  Ideally we'd prioritize them
but the order of IPC and LoadingTasks currently needs to
be more or less in lockstep.  Instead we deprioritize compositor
tasks inside a compositor gesture, which has the effect of
prioritizing other work.

Expected changes on Perf bots:
1. first_gesture_scroll_update_latency in smoothness.scrolling_tough_ad_cases
should go down.  This should be highly user visible.
2. It's possible some compositor metrics such as queueing_durations
may regress.  I don't expect this to be user visible.

This is a reland of https://codereview.chromium.org/1320633002.

Original author: Alex Clarke <[email protected]>;

BUG=510398, 530250
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
[email protected]

Committed: https://crrev.com/262700e6bbb78cc2348b5ed86326de9bfaeded21
Cr-Commit-Position: refs/heads/master@{#348886}

[Sami, 2015-09-14 18:05:34]

[email protected] changed reviewers:
+ [email protected]

[Sami, 2015-09-14 18:10:52]

This is a reland of Alex's user model patch enhanced with fixes for the
windows-only test flakes. tl;dr: we were using the wall clock instead of the
simulated test clock for task cost estimation. Since windows has less timer
precision it sometimes thought these tasks were infinitely fast. D'oh!

[Sami, 2015-09-14 18:11:36]

(TBR'ing content/renderer/render_frame_impl.cc since it's unchanged for last
time.)

[Sami, 2015-09-15 13:03:29]

(In case it wasn't obvious, it's the diff from patch set #1 to #2 that needs
reviewing here.)

[rmcilroy, 2015-09-15 13:43:15]

lgtm, thanks.

[Sami, 2015-09-15 13:43:36]

The CQ bit was checked by [email protected]

[commit-bot: I haz the power, 2015-09-15 13:43:45]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1340073003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1340073003/20001

[commit-bot: I haz the power, 2015-09-15 14:54:30]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-09-15 14:55:22]

Patchset 2 (id:??) landed as
https://crrev.com/262700e6bbb78cc2348b5ed86326de9bfaeded21
Cr-Commit-Position: refs/heads/master@{#348886}

[commit-bot: I haz the power, 2015-09-23 12:44:57]

Patchset 2 (id:??) landed as
https://crrev.com/262700e6bbb78cc2348b5ed86326de9bfaeded21
Cr-Commit-Position: refs/heads/master@{#348886}