Remove unnecessary fields from the MeshBVHNode to save memory about three-mesh-bvh HOT 4 CLOSED

It's possible that removing fields conditionally (and thereby making all the nodes not have homogeneous shapes) could hurt performance due to JIT inline caching, so it's worth benchmarking after this to make sure there's not a regression.

from three-mesh-bvh.

That's a good point. If it does wind up being slower then having two different classes may be a better option? One with children and one with tris?

I'll also have to see how much removing a key really saves here. I'm not so familiar with how to estimate memory use when it comes to javascript object keys.

from three-mesh-bvh.

No idea if the objects having the same prototype will make a difference or not.

Removing children is particularly appealing since for leaf nodes it's an empty array, so we're paying memory twice -- once for the pointer and once for the empty array. tris is just null for non-leaves so we only pay for the pointer.

from three-mesh-bvh.

Most unneeded fields removed in #44

from three-mesh-bvh.