# Maximum limit for indexes

**URL:** <https://discuss.elastic.co/t/maximum-limit-for-indexes/6828>\
**Category:** Elasticsearch\
**Created:** [February 28, 2012, 10:48am UTC](https://discuss.elastic.co/t/maximum-limit-for-indexes/6828 "2012-02-28T10:48:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [July 18, 2012, 8:57am UTC](https://discuss.elastic.co/t/maximum-limit-for-indexes/6828/4 "2012-07-18T08:57:57Z")

</div>

Hi Jim

> Could you elaborate a bit on the overhead of indices? A single  
> index-per-object is gives us a perfect setup for our dataflow, but how  
> far can this scale reasonably? Though we're starting out at ~20,000  
> indices, I'd like to be able to plan for 1 million if possible.
> 
> If this isn't too far fetched, which is the more important scaling  
> factor, node size or node count?

That is indeed far fetched 🙂 Unless you plan on having hundreds of  
thousands of servers...

However, filtered aliases might be what you are after.

I suggest taking a look at Shay's presentation at berlin buzzwords this  
year:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

clint

> Thanks,  
> -jim

---

_[View the full topic](https://discuss.elastic.co/t/maximum-limit-for-indexes/6828)._