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
childVDOMs() might be a current bottleneck (in the JS/React part, very negligible when comparing with the GL part which is much more intensive)
a simple way to optimize this is to compute the "children vdoms" once for each data node, and just make this an accessor.
because currently, as we going down the tree, we are recomputing again everything
The text was updated successfully, but these errors were encountered:
childVDOMs()
might be a current bottleneck (in the JS/React part, very negligible when comparing with the GL part which is much more intensive)a simple way to optimize this is to compute the "children vdoms" once for each data node, and just make this an accessor.
because currently, as we going down the tree, we are recomputing again everything
The text was updated successfully, but these errors were encountered: