# Index with a large number of document types?

**URL:** <https://discuss.elastic.co/t/index-with-a-large-number-of-document-types/12970>\
**Category:** Elasticsearch\
**Created:** [July 27, 2013, 11:38pm UTC](https://discuss.elastic.co/t/index-with-a-large-number-of-document-types/12970 "2013-07-27T23:38:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![no\_computer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/no_computer/32/2199_2.png) [@no\_computer](https://discuss.elastic.co/u/no_computer)\
**Post date:** [July 27, 2013, 11:38pm UTC](https://discuss.elastic.co/t/index-with-a-large-number-of-document-types/12970/1 "2013-07-27T23:38:35Z")

</div>

My app needs user based searching, most users will have a small number of documents, so I think index-per-user design is probably not a good idea. I am considering using document type per user architecture. For example:

documents/document-user1  
documents/document-user2  
documents/document-user3

The number of users can potentially be large, is there any performance problems or disadvantages for an index with hundreds of thousands of mapping types ?

Thanks,  
Peng

---

<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, 2:24am UTC](https://discuss.elastic.co/t/index-with-a-large-number-of-document-types/12970/2 "2017-07-06T02:24:08Z")

</div>

Closed on July 6, 2017, 2:24am UTC