# Elasticsearch storage usage **URL:** \ **Category:** Elasticsearch\ **Created:** [December 26, 2012, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175 "2012-12-26T08:33:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)\ **Post date:** [December 26, 2012, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/1 "2012-12-26T08:33:11Z")
I am working on an application where I am using elasticsearch as the primary database, I have been running some inserts on an index and seeing 3x database storage increases over the raw files. I am not sure if this is normally of a full text search system, Is there anything i can do to make some things less searchable or able to keep the datasize smaller. -- ---
**Author:** ![Artem\_Grinblat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_grinblat/32/2327_2.png) [@Artem\_Grinblat](https://discuss.elastic.co/u/Artem_Grinblat)\ **Post date:** [December 26, 2012, 12:37pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/2 "2012-12-26T12:37:17Z")
Lucene indexes are a form of an append-only database: new data is inserted into a new file, then after certain conditions are met the index is compacted by merging several files together into yet another file while skipping the removed entries. That means there are old versions of data lying around until compaction. I think you can tune the ES to do the Lucene compactions more often. There's also index compression, cf. [https://groups.google.com/d/msg/elasticsearch/3hNu6GPd4pE/I0Kcm\_inyHQJ](https://groups.google.com/d/msg/elasticsearch/3hNu6GPd4pE/I0Kcm_inyHQJ) And of course the inverted indexes have some overhead of their own as they need to store document ids and statistics for every term. Just my two cents. среда, 26 декабря 2012 г., 12:33:11 UTC+4 пользователь Wojons Tech написал: > I am working on an application where I am using elasticsearch as the > primary database, I have been running some inserts on an index and seeing > 3x database storage increases over the raw files. I am not sure if this is > normally of a full text search system, Is there anything i can do to make > some things less searchable or able to keep the datasize smaller. -- ---
**Author:** ![Artem\_Grinblat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_grinblat/32/2327_2.png) [@Artem\_Grinblat](https://discuss.elastic.co/u/Artem_Grinblat)\ **Post date:** [December 26, 2012, 12:41pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/3 "2012-12-26T12:41:56Z")
AFAIK, Lucene has one of the most compact index formats. Other full-text search engines usually have bigger indexes. See, for example, [http://taschenorakel.de/mathias/2012/04/18/fulltext-search-benchmarks/](http://taschenorakel.de/mathias/2012/04/18/fulltext-search-benchmarks/) > I am not sure if this is normally of a full text search system -- ---
**Author:** ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)\ **Post date:** [December 26, 2012, 1:18pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/4 "2012-12-26T13:18:07Z")
Okay that makes sense i am seeing the documents size rati going down its much closer now to using twice as much space and not more than that. On Wednesday, December 26, 2012 4:41:56 AM UTC-8, Artem Grinblat wrote: > AFAIK, Lucene has one of the most compact index formats. Other full-text > search engines usually have bigger indexes. See, for example, > [http://taschenorakel.de/mathias/2012/04/18/fulltext-search-benchmarks/](http://taschenorakel.de/mathias/2012/04/18/fulltext-search-benchmarks/) > > > I am not sure if this is normally of a full text search system -- ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [December 27, 2012, 4:07pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/5 "2012-12-27T16:07:23Z")
Hi, You also probably have \_source enabled and maaay have individual fields marked as stored and maybe you also have \_all? ## Otis ELASTICSEARCH Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) On Wednesday, December 26, 2012 3:33:11 AM UTC-5, Wojons Tech wrote: > I am working on an application where I am using elasticsearch as the > primary database, I have been running some inserts on an index and seeing > 3x database storage increases over the raw files. I am not sure if this is > normally of a full text search system, Is there anything i can do to make > some things less searchable or able to keep the datasize smaller. -- ---
**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:58am UTC](https://discuss.elastic.co/t/elasticsearch-storage-usage/10175/6 "2017-07-06T02:58:22Z")