# Maximum number of indices in a single Node for optimal performance

**URL:** <https://discuss.elastic.co/t/maximum-number-of-indices-in-a-single-node-for-optimal-performance/31820>\
**Category:** Elasticsearch\
**Created:** [October 8, 2015, 6:36am UTC](https://discuss.elastic.co/t/maximum-number-of-indices-in-a-single-node-for-optimal-performance/31820 "2015-10-08T06:36:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![srkhanzode](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@srkhanzode](https://discuss.elastic.co/u/srkhanzode)\
**Post date:** [October 8, 2015, 6:36am UTC](https://discuss.elastic.co/t/maximum-number-of-indices-in-a-single-node-for-optimal-performance/31820/1 "2015-10-08T06:36:45Z")

</div>

Hi,

Assuming some standard hardware, like say, a 16 core CPU and 64 GB RAM, can we come up with some statistics that tell us the maximum indices that can be gracefully supported.

Assuming every index has 5 shards.  
The size and counts will be variable per index, however, assuming ~15M documents for a total size of ~30-50 GB.

Is it safe to believe that a smaller consolidated number of indices holding equivalent aggregate data of a large number of indices would perform better? Seems the indexing performance may benefit, but does it also apply to real-time search performance?

What are the prohibiting factors that limit performance when an unreasonable number of indices are created per node? I believe Index Management is a big deal for an EL node.

Thanks,  
Sandeep

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:45pm UTC](https://discuss.elastic.co/t/maximum-number-of-indices-in-a-single-node-for-optimal-performance/31820/2 "2017-07-05T23:45:57Z")

</div>

Closed on July 5, 2017, 11:45pm UTC