-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
chore: improve performance of scheduling effects (but without creating additional branches) #13300
Conversation
🦋 Changeset detectedLatest commit: e200487 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 |
Awesome :) |
Ah, with this PR I get this error when running the reactivity benchmark locally running all the benchmarks together. RangeError: Maximum call stack size exceeded
at check_dirtiness ([stdin]:823:25)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13)
at check_dirtiness ([stdin]:841:13) If I remove the Update: I was only running a subset of the benchmarks. Running them all together and it seems to work fine? |
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.
Removing my approval for now
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.
So I think there was an issue with how I was benchmarking, it seems to be fine now.
Another take on #13282 — rather than creating an additional branch effect for every
effect_root
, this just flags roots as being queued and avoids queuing them a second time. On flush, the flag is removed.