# Elasticsearch- Single Index vs Multiple Indexes

**URL:** <https://discuss.elastic.co/t/elasticsearch-single-index-vs-multiple-indexes/164265>\
**Category:** Elasticsearch\
**Created:** [January 15, 2019, 8:39am UTC](https://discuss.elastic.co/t/elasticsearch-single-index-vs-multiple-indexes/164265 "2019-01-15T08:39:33Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [January 16, 2019, 9:32am UTC](https://discuss.elastic.co/t/elasticsearch-single-index-vs-multiple-indexes/164265/18 "2019-01-16T09:32:28Z")

</div>

> [@pranav24](#):
>
> can there be chances of mapping explosion?

As I defined to your colleague Nikesh [here](https://discuss.elastic.co/t/elastic-mapping-explosion/162647/11), I consider a "mapping explosion" to not be a specific event but a general condition of having a lot of fields.

By that definition, yes, you will have a lot of fields.

If you want to consider the impact of field numbers on something more specific (query response times, disk space, RAM utilisation, indexing speeds...) I suggest you perform some benchmarking.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-single-index-vs-multiple-indexes/164265)._