Skip to content

Commit 75ab53b

Browse files
authored
[scheduler] Yield many times per frame, no rAF (#16214)
Adds experimental flag to yield many times per frame using a message event loop, instead of the current approach of guessing the next vsync and yielding at the end of the frame. This new approach forgoes a `requestAnimationFrame` entirely. It posts a message event and performs a small amount of work (5ms) before yielding to the browser, regardless of where it might be in the vsync cycle. At the end of the event, if there's work left over, it posts another message event. This should keep the main thread responsive even for really high frame rates. It also shouldn't matter if the hardware frame rate changes after page load (our current heuristic only detects if the frame rate increases, not decreases). The main risk is that yielding more often will exacerbate main thread contention with other browser tasks. Let's try it and see.
1 parent 0d7141d commit 75ab53b

File tree

5 files changed

+538
-414
lines changed

5 files changed

+538
-414
lines changed

packages/scheduler/src/SchedulerFeatureFlags.js

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,4 @@ export const enableSchedulerDebugging = false;
1010
export const enableIsInputPending = false;
1111
export const requestIdleCallbackBeforeFirstFrame = false;
1212
export const requestTimerEventBeforeFirstFrame = false;
13+
export const enableMessageLoopImplementation = false;

0 commit comments

Comments
 (0)