-
Notifications
You must be signed in to change notification settings - Fork 47.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable MessageLoop implementation by default #16408
Conversation
React: size: -2.3%, gzip: -3.1% Details of bundled changes.Comparing: 868d02d...d61c6cc react
scheduler
Generated by 🚫 dangerJS |
Maybe we need to make sure this works on RN now? |
Let's go ahead and merge this? |
Lemme check RN. What are we looking for? Just that effects fire? |
React: size: -2.2%, gzip: -2.8% Details of bundled changes.Comparing: 79e46b6...1773240 react
scheduler
|
I tested on RN a bit. useEffect works. |
famous last words 😄 |
Is this change published on the latest or any of the pre-releases? |
This disables the RAF scheduler impl in favor of the MessageLoop one, which we've found better utilizes CPU. Unlike #16271, this keeps the RAF implementation for now just in case, but it's only in one specially marked test.
This matches what we already rolled out in www, except the rAF-specific flags (they're true on www but they're dead code in the rAF path anyway — and I didn't want to adjust the test for them).
My previous PR includes most of the extra test coverage for ML scheduler which I picked up from Andrew's earlier PR.