Skip to content
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

Merged
merged 19 commits into from
Sep 18, 2024

Conversation

Rich-Harris
Copy link
Member

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.

Copy link

changeset-bot bot commented Sep 18, 2024

🦋 Changeset detected

Latest commit: e200487

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

@trueadm
Copy link
Contributor

trueadm commented Sep 18, 2024

Awesome :)

@trueadm
Copy link
Contributor

trueadm commented Sep 18, 2024

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 EFFECT_QUEUED logic or move the the bit where we change the flag off to after the flushing then the benchmark works (but our tests fail). I'll need some time to dig into this.

Update: I was only running a subset of the benchmarks. Running them all together and it seems to work fine?

Copy link
Contributor

@trueadm trueadm left a 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

Copy link
Contributor

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

@trueadm trueadm merged commit b441738 into main Sep 18, 2024
9 checks passed
@trueadm trueadm deleted the schedule_effect_perf_without_branch branch September 18, 2024 09:09
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.

2 participants