Replies: 1 comment
-
https://deck.gl/docs/developer-guide/using-layers#should-i-be-creating-new-layers-on-every-render |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Body:
I'm using PathLayer from deck.gl to render map path data. In my application, I need to frequently update the data of the layer, and I've noticed that every time I update the data, a new layer instance is created. This leads to an issue of increasing browser memory usage over time.
I'd like to know how to avoid creating unnecessary new layer instances when updating the layer data. Is there a way to directly update the properties of the existing layer instance without creating a new one?
If there are any feasible methods or best practices, please provide some guidance so that I can optimize my application and reduce the increase in memory usage.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions