Debounce tree updates#809
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: fc7bcd1 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 |
Micheal Parks (micheal-parks)
requested review from
Devin T. Currie (DTCurrie),
Matthew MacFarquhar (mattmacf98) and
Marcus (sucrammal)
Contributor
|
Matthew MacFarquhar (mattmacf98)
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
In scenes that have very rapid add / remove cycles, a major CPU bottleneck becomes rebuilding the treeview. In one scene I observed, around 8,000 dom nodes were being replaced per frame, grinding framerate down to around 6fps.
This PR simply debounces updates to around every 100ms. This is still faster than pretty much anyone is going to perceive. The result of the same scene is a much higher framerate. See the performance profiler in the top right.
Before:
After: