# A single document type per index to increase performance?

**URL:** <https://discuss.elastic.co/t/a-single-document-type-per-index-to-increase-performance/20528>\
**Category:** Elasticsearch\
**Created:** [November 1, 2014, 4:01pm UTC](https://discuss.elastic.co/t/a-single-document-type-per-index-to-increase-performance/20528 "2014-11-01T16:01:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Antoine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/antoine/32/1135_2.png) [@Antoine](https://discuss.elastic.co/u/Antoine)\
**Post date:** [November 1, 2014, 4:01pm UTC](https://discuss.elastic.co/t/a-single-document-type-per-index-to-increase-performance/20528/1 "2014-11-01T16:01:10Z")

</div>

Hi,

Do you know if separate document of different type into distinct indexes  
could increase search requests performance?  
An Elasticsearch expert told it:  
\*"\*\*To maximize performance, minimize memory usage and make a significant  
index, we must never make the multi-purpose, ie include several 'types' of  
documents in a single index. The recommended strategy is to make an index  
by document type, so as to retrieve the desired information so registered  
without golf insignificant data. This separation of data has no negative  
impact on performance, \*_quite the contrary."_

What do you think about this recommandation?

Regards,

Antoine

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e6fc7bac-bdd3-47a3-840f-fe24de066b14%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e6fc7bac-bdd3-47a3-840f-fe24de066b14%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Telax](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@Telax](https://discuss.elastic.co/u/Telax)\
**Post date:** [November 2, 2014, 9:38am UTC](https://discuss.elastic.co/t/a-single-document-type-per-index-to-increase-performance/20528/2 "2014-11-02T09:38:18Z")

</div>

Can your system handle the memory overhead of many additional active Lucerne instances (shards)?

How often do you search across multiple types (either with \_all or a common field).

If the answer is yes to the first and not at all to the second then splitting your data types into different indexes does make sense.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2d4a47c7-569c-42e5-8400-3506752712a0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2d4a47c7-569c-42e5-8400-3506752712a0%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:52am UTC](https://discuss.elastic.co/t/a-single-document-type-per-index-to-increase-performance/20528/3 "2017-07-06T00:52:38Z")

</div>