generated from tc39/template-for-proposals
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Really bad unwatch
performance (3000%)
#215
Comments
Thanks for reporting this! PRs welcome to improve performance. |
Linking one more issue: proposal-signals/signal-polyfill#2 |
btakita
added a commit
to btakita/briantakita.me
that referenced
this issue
Jun 4, 2024
btakita
added a commit
to btakita/briantakita.me-dev
that referenced
this issue
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! Thank you for great work and all movements here!
I'm maintainer of https://github.com/lifeart/glimmer-next (glimmer-vm runtime alternative for Ember)
Repo using reactive approach very close to signals, based on this reactivity concept: lifeart/glimmer-next#41
I'm trying to be more
native
and experimenting with drop-in replacement with signals polyfill.During testing I observe 10x performance degradation, especially on
cleanup
cases:clearManyItems1End phase estimated regression +3750ms [3727ms to 3783ms] OR +3214.31% [3194.71% to 3242.69%]
artifact-1.pdf
here is PR i'm testing on: lifeart/glimmer-next#114
The text was updated successfully, but these errors were encountered: