-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix: improve controlled each block cleanup performance #11839
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
Conversation
🦋 Changeset detectedLatest commit: a0316e8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Have often wondered if we couldn't |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How much perf loss are we talking about by not using a default argument? If it's 1% in a function that takes 0.01ms then I think the bundle size concerns outweigh the benefit.
This PR improves controlled each block cleanup by around 8-26%, depending on the size of the subtree. If we can avoid calls to
node.isConnected
then it all adds up.