| commit | ecee08ee7b6facd3c8ae2257abc9d83a19be705a | |
| author | jbauman <jbauman@chromium.org> | |
| Thu, 12 Mar 2015 21:09:31 +0000 (12 14:09 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 12 Mar 2015 21:10:19 +0000 (12 21:10 +0000) | ||
| tree | 16c8e46769c41afccc46ca326a171ee5f6e74bc4 | treesnapshot (tar.gz zip) |
| parent | 5235011aa967a55221029e0558b8b7ce86bc88a4 | commitdiff |
Put renderer contents in separate Surface on Android
When Surfaces are enabled on Android (still disabled by default) put the renderer contents into its own Surface instead of using a delegated layer on the browser compositor. This causes it to be scheduled and aggregated directly through the Display, which should reduce CPU usage and latency.
BUG=334090,449319
Review URL: https://codereview.chromium.org/725943003
Cr-Commit-Position: refs/heads/master@{#320372}
When Surfaces are enabled on Android (still disabled by default) put the renderer contents into its own Surface instead of using a delegated layer on the browser compositor. This causes it to be scheduled and aggregated directly through the Display, which should reduce CPU usage and latency.
BUG=334090,449319
Review URL: https://codereview.chromium.org/725943003
Cr-Commit-Position: refs/heads/master@{#320372}