GitLab

Chrome's handling of latency sensitive tasks such as video playback can
easily be affected by the frequency of the Windows timer interrupt. This
timer interrupt is a global resource and any process can raise its
frequency. Previously this would affect thread scheduling for all
processes but with Windows 10 2004 Microsoft appears to try to simulate
"normal" thread scheduling in processes that did not themselves alter
the timer interrupt frequency.

This is suspected of causing frame drops during video playback. The
easiest way to rule out this as the cause is to get all Chrome processes
to raise the timer interrupt frequency to the maximum level so that they
will all get scheduled according to that raised frequency.

This flag should not be generally used and may be removed in the future.

Bug: 1128917
Change-Id: I97fddebab251240fdb6181d6960b0dea86b9f0b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458854
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#815530}