Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Proxies for reactivity are ruining performance

See original GitHub issue

Reduced Test Case: https://codepen.io/cferdinandi/pen/VwMpoYQ

If you click the Swap Wizards button a few times, it works fine. If you focus on the button and hold the enter/return key down to trigger a swap multiple times, the nested proxy structure overloads the browser and freezes the app.

Switching to a setter function style approach as the only way to update reactively would dramatically improve performance.

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

cferdinandicommented, Dec 17, 2021

Patched in 10.0.1

0reactions

cferdinandicommented, Dec 20, 2021

@pranav-js please open a new issue for this

Top Results From Across the Web

Debunking myths: proxies impact performance - Spring

Because the proxy sits in between the caller of an object and the real object itself, it can decide to prevent the real...

Common problems with reactivity · Issue #849 · vuejs/docs

The proxy-based reactivity can be a massive performance boost with some third-party libraries, so it isn't all bad news from that ...

The Magic Behind Reactivity - Effects - Ryan Chandler

In this post, I'll be creating an effect function that will allow us to react to changes on the Proxy and update the...

When Vue Meets Proxy - Level Up Coding

JS to Reveal How It Uses Proxy to Achieve Reactivity ... Performance: for a large and/or nested data set, performance could be negatively...

The fundamental principles behind MobX | by Michel Weststrate

Finally, nx-observe proves that proxies are very viable foundation for a transparent reactive programming library. Both conceptually and performance wise.