Skip to content

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

Merged
merged 6 commits into from
May 31, 2024

Conversation

trueadm
Copy link
Contributor

@trueadm trueadm commented May 30, 2024

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.

Copy link

changeset-bot bot commented May 30, 2024

🦋 Changeset detected

Latest commit: a0316e8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

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

@Rich-Harris
Copy link
Member

Have often wondered if we couldn't skip_remove_dom on all child effects, rather than saving this optimisation for controlled each blocks — seems it would be a lot more efficient that way. Which I guess is another reason to try and land #11690

Copy link
Member

@dummdidumm dummdidumm left a 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.

@dummdidumm dummdidumm merged commit 3c84c21 into main May 31, 2024
8 checks passed
@dummdidumm dummdidumm deleted the improve-controlled branch May 31, 2024 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants