perf(reactivity): avoid unnecessary recursion in removeSub #12135
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.
I stumbled across an edge case where the performance of
computed
can go awry:The time taken grows exponentially with the value of
LAYERS
. I used22
in the example, but you may need to tweak it depending on your hardware.The problem is with cleaning up the subs.
removeSub()
calls itself recursively ifdep.subs
isundefined
. But in this example,deps.subs
is alwaysundefined
for alldeps
, so it ends up callingremoveSub()
a huge number of times. The same links are being removed over and over.I've attempted to fix it by additionally checking that
deps.subs
wasn't alreadyundefined
.The diff makes the change look more complicated than it actually is. I've moved the
if (dep.subs === link) {
part further down and wrapped it around the clean-up section.