cc: Aggressively expire retro frames.

cc: Aggressively expire retro frames.

If we're not aggressive about expiring a retro frame (e.g. MISSED
frames) then it's possible to enter a high latency mode often.

PixelTestOutputSurface is used by the ui compositor in tests and we
should not subtract the default estimated parent draw time from the
deadline in that case. Doing so will cause MISSED frames to always
expire in tests.

BUG=469953
Committed: https://crrev.com/7e4f0459fd2d0af0e1b5a6a5069465862afb5bae
Cr-Commit-Position: refs/heads/master@{#330669}

[sunnyps, 2015-04-16 02:06:59]

sunnyps@chromium.org changed reviewers:
+ brianderson@chromium.org

[sunnyps, 2015-04-16 02:06:59]

PTAL

[brianderson, 2015-04-16 17:39:17]

lgtm

[brianderson, 2015-05-18 20:31:31]

Sunny, I tried this patch with the DisplayScheudler and it improves Browser
scheduling a ton by preventing late Browser commits from eating into the
deadline.

I suspect it will be a win for the Renderer too.

Is this landable?

[sunnyps, 2015-05-18 20:39:01]

On 2015/05/18 20:31:31, brianderson wrote:
> Sunny, I tried this patch with the DisplayScheudler and it improves Browser
> scheduling a ton by preventing late Browser commits from eating into the
> deadline.
> 
> I suspect it will be a win for the Renderer too.
> 
> Is this landable?

This is landable - I wasn't able to get definitive performance numbers when I
tested this on a Nexus 5. The noise from thermal throttling made the testing
unreliable. Maybe we CQ this and see what happens on the perf bots?

[brianderson, 2015-05-18 20:41:12]

Yeah. I think this will be a win - let's see what happens.

[sunnyps, 2015-05-18 20:45:35]

The CQ bit was checked by sunnyps@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-05-18 20:47:24]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1055113004/1

[commit-bot: I haz the power, 2015-05-19 00:22:45]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-19 00:22:46]

Dry run: This issue passed the CQ dry run.

[sunnyps, 2015-05-19 01:00:49]

The CQ bit was checked by sunnyps@chromium.org

[commit-bot: I haz the power, 2015-05-19 01:01:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1055113004/1

[commit-bot: I haz the power, 2015-05-19 01:04:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-19 01:05:23]

Patchset 1 (id:??) landed as
https://crrev.com/bb5a390066a1baf27ec44228fd3ba4173f93cfbf
Cr-Commit-Position: refs/heads/master@{#330465}

[Thiemo Nagel, 2015-05-19 11:36:25]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1135003006/ by tnagel@chromium.org.

The reason for reverting is: This seems to be causing
DesktopNativeWidgetNoPaintAfterCloseTest failures..

[sunnyps, 2015-05-19 23:33:43]

The CQ bit was checked by sunnyps@chromium.org

[sunnyps, 2015-05-19 23:33:43]

The patchset sent to the CQ was uploaded after l-g-t-m from
brianderson@chromium.org
Link to the patchset: https://codereview.chromium.org/1055113004/#ps20001
(title: "Do not adjust deadline")

[sunnyps, 2015-05-19 23:33:47]

The CQ bit was unchecked by sunnyps@chromium.org

[sunnyps, 2015-05-19 23:37:07]

The CQ bit was checked by sunnyps@chromium.org

[commit-bot: I haz the power, 2015-05-20 00:21:00]

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

[commit-bot: I haz the power, 2015-05-20 01:44:08]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-05-20 01:45:02]

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