# Compression Mechanism

**URL:** <https://discuss.elastic.co/t/compression-mechanism/19184>\
**Category:** Elasticsearch\
**Created:** [August 11, 2014, 6:01am UTC](https://discuss.elastic.co/t/compression-mechanism/19184 "2014-08-11T06:01:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hiveesuser](https://avatars.discourse-cdn.com/v4/letter/h/5f8ce5/32.png) [@hiveesuser](https://discuss.elastic.co/u/hiveesuser)\
**Post date:** [August 11, 2014, 6:01am UTC](https://discuss.elastic.co/t/compression-mechanism/19184/1 "2014-08-11T06:01:57Z")

</div>

I am using elasticsearch as medium to store my data what is the compression  
meachnism used in storing the data.

The reason why I am asking is if I have 50 GB of raw data coming in every  
day how much should I plan for my hardware diskspace that's the reason I  
want to know how this one works

--  
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/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 11, 2014, 6:04am UTC](https://discuss.elastic.co/t/compression-mechanism/19184/2 "2014-08-11T06:04:59Z")

</div>

Data use will depend on your indexing rate and how big your documents are,  
which is entirely dependant on your use.

However ES uses the lz4 compression algorithm.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 11 August 2014 16:01, [hiveesuser@gmail.com](mailto:hiveesuser@gmail.com) wrote:

> I am using elasticsearch as medium to store my data what is the  
> compression meachnism used in storing the data.
> 
> The reason why I am asking is if I have 50 GB of raw data coming in every  
> day how much should I plan for my hardware diskspace that's the reason I  
> want to know how this one works
> 
> --  
> 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/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/18648a47-04df-4ae0-8f52-98d61d1f6d6a%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEM624a28pzaYBJHT0j5PU0pRtmxN%2BBkZfksv-JrM2To285Crg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a28pzaYBJHT0j5PU0pRtmxN%2BBkZfksv-JrM2To285Crg%40mail.gmail.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:** [August 12, 2014, 6:49am UTC](https://discuss.elastic.co/t/compression-mechanism/19184/3 "2014-08-12T06:49:47Z")

</div>

ElasticSearch uses LZF on stored fields (including \_source). The storage requirements will depend on your implementation and the complexity of your data, however, planning for a 1:1 ratio +10% with compression enabled aught to put you on the right path. Otherwise, you'll have to experiment to find out exactly what you'll require.

--  
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/64ccbc7e-0fb9-4c7b-ae23-8c69cbd32ca4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/64ccbc7e-0fb9-4c7b-ae23-8c69cbd32ca4%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [August 12, 2014, 6:56am UTC](https://discuss.elastic.co/t/compression-mechanism/19184/4 "2014-08-12T06:56:40Z")

</div>

Elasticsearch uses LZ4, see  
[http://blog.jpountz.net/post/35667727458/stored-fields-compression-in-lucene-4-1](http://blog.jpountz.net/post/35667727458/stored-fields-compression-in-lucene-4-1)

For storage requirements, you need around twice the disk space if you  
incrementally grow your index, because of additional segment merge space  
overhead.

Jörg

On Tue, Aug 12, 2014 at 8:49 AM, Telax [andrew.w.nixon@gmail.com](mailto:andrew.w.nixon@gmail.com) wrote:

> Elasticsearch uses LZF on stored fields (including \_source). The storage  
> requirements will depend on your implementation and the complexity of your  
> data, however, planning for a 1:1 ratio +10% with compression enabled aught  
> to put you on the right path. Otherwise, you'll have to experiment to find  
> out exactly what you'll require.
> 
> --  
> 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/64ccbc7e-0fb9-4c7b-ae23-8c69cbd32ca4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/64ccbc7e-0fb9-4c7b-ae23-8c69cbd32ca4%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAKdsXoEu8aVh%2BiSGXwfUutrTRHJ4cQzzW2-36OpVP3-nd%2B200Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEu8aVh%2BiSGXwfUutrTRHJ4cQzzW2-36OpVP3-nd%2B200Q%40mail.gmail.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, 1:09am UTC](https://discuss.elastic.co/t/compression-mechanism/19184/5 "2017-07-06T01:09:22Z")

</div>


