You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Lightning there's logic to reuse textures and garbage collection mechanism to free unusued textures and reuse them when possible since it's quite computationally intensive to re-create them all the time.
We've noticed that extensive computation is also caused by component instantiation. Hence we were wondering whether similar logic could be applied to components instances as well.
We're trying to implement this at the app-level but it's getting quite convoluted and we were wondering if there was an easy way to avoid instantiating specific component types and instead reuse them from a pool of "unused" ones.
Thoughts?
The text was updated successfully, but these errors were encountered:
In Lightning there's logic to reuse textures and garbage collection mechanism to free unusued textures and reuse them when possible since it's quite computationally intensive to re-create them all the time.
We've noticed that extensive computation is also caused by component instantiation. Hence we were wondering whether similar logic could be applied to components instances as well.
We're trying to implement this at the app-level but it's getting quite convoluted and we were wondering if there was an easy way to avoid instantiating specific component types and instead reuse them from a pool of "unused" ones.
Thoughts?
The text was updated successfully, but these errors were encountered: