# Consequences of a Large Index Size

**URL:** <https://discuss.elastic.co/t/consequences-of-a-large-index-size/124257>\
**Category:** Elasticsearch\
**Created:** [March 16, 2018, 10:04am UTC](https://discuss.elastic.co/t/consequences-of-a-large-index-size/124257 "2018-03-16T10:04:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ong/32/40766_2.png) [@Ong](https://discuss.elastic.co/u/Ong)\
**Post date:** [March 16, 2018, 10:04am UTC](https://discuss.elastic.co/t/consequences-of-a-large-index-size/124257/1 "2018-03-16T10:04:48Z")

</div>

I have an index which is 2.5 times larger than the raw data size. The estimated index size is around 6TB for 40 million text documents. A key reason for this is the use of shingles.

I have a few concerns about having a large index size, including long re-index times during version upgrades or index recovery. Are there other areas to be concerned about for large indexes? e.g. indexing speed, search speed, stability of Elastic search etc. ?

I am thinking of enabling compression for the indexes to save some storage space. Is compression enabled by default in Elasticsearch?

---

<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:** [April 13, 2018, 10:04am UTC](https://discuss.elastic.co/t/consequences-of-a-large-index-size/124257/2 "2018-04-13T10:04:55Z")

</div>

Closed on April 13, 2018, 10:04am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.