[scheduler] Enabling rendering prioritization by default.
Previously, the blink scheduler would run rendering at the same priority as most work on the main thread (eg. postMessage, timers, ect.) which could leave rendering to get starved by other tasks and cause visual lag.This change periodically prioritizes rendering, targeting a lower frame rate of 10 fps, in order to prevent rendering starvation (fixing issues like crbug.com/921335 and crbug.com/943621). Given good results during experimentation, we have decided to enable this behavior by default. This CL also has a small implementation change, using a TickClock to measure time between compositor tasks instead of posting a delayed task to serve as a countdown. Bug: 966177 Change-Id: I4956a9f5dbfb7258d8fdc8ad45e74f62db8917b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030124 Commit-Queue: Katie Dillon <kdillon@chromium.org> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Scott Haseley <shaseley@chromium.org> Cr-Commit-Position: refs/heads/master@{#737132}
Showing
Please register or sign in to comment