-
-
Notifications
You must be signed in to change notification settings - Fork 42
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Use a single ResizeObserver instance #24
Comments
Related – #26 |
I'm not convinced yet whether this is an optimisation that's actually worth it or not. I'd need a way to test this somehow for myself for a large number of observed elements and measure CPU / memory usage maybe, to see if there's a difference between using one or many RO instances. |
Or if there was a comprehensive test / article / benchmark that demonstrated that using a single RO instance is significantly better, then I would consider it. |
I forgot about this one: Seems like there's something in there, but I'd still need a way to benchmark CPU + memory usage, so that I could compare a results of the current implementation to one that uses a single instance. |
I'd really appreciate someone well-versed in benchmarking UI to help out. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Seems like it's more performant and the recommended pattern:
WICG/resize-observer#59
The text was updated successfully, but these errors were encountered: