# InstancedMesh optimation with Tiles culling?

**URL:** <https://discourse.threejs.org/t/instancedmesh-optimation-with-tiles-culling/15271>\
**Category:** Questions\
**Created:** [May 16, 2020, 3:17pm UTC](https://discourse.threejs.org/t/instancedmesh-optimation-with-tiles-culling/15271 "2020-05-16T15:17:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Fyrestar](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/fyrestar/32/52793_2.png) [@Fyrestar](https://discourse.threejs.org/u/Fyrestar)\
**Post date:** [May 16, 2020, 3:29pm UTC](https://discourse.threejs.org/t/instancedmesh-optimation-with-tiles-culling/15271/2 "2020-05-16T15:29:01Z")

</div>

Using clusters is one way you can do it, but 256 doesn’t sound like too many. For the [IndexedVolume](https://discourse.threejs.org/t/tesseract-open-world-planetary-engine/1473/9) i use auto-instancing with culling as well as clusters stored in nodes for specific kind of assets, but it requires a lot for it to pay off.

---

_[View the full topic](https://discourse.threejs.org/t/instancedmesh-optimation-with-tiles-culling/15271)._