# Compression Factor in Document Size **URL:** \ **Category:** Elasticsearch\ **Created:** [February 13, 2017, 2:13pm UTC](https://discuss.elastic.co/t/compression-factor-in-document-size/74890 "2017-02-13T14:13:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\ **Post date:** [February 13, 2017, 2:13pm UTC](https://discuss.elastic.co/t/compression-factor-in-document-size/74890/1 "2017-02-13T14:13:01Z")
Hi, I wanted to understand what is the compression logic followed in Elastic Search for storing of documents? Any documentation which describes the compression factor would be really helpful in scaling ES for anticipated write load. ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [February 13, 2017, 4:46pm UTC](https://discuss.elastic.co/t/compression-factor-in-document-size/74890/2 "2017-02-13T16:46:40Z")
Hi, Although this [blog post](https://www.elastic.co/blog/store-compression-in-lucene-and-elasticsearch) is a bit old, it might give you a start to understand some of the issues at play here. I think in the end there is no such thing as a fixed number, the size used on disc will depend on the kind of data and the analysis it undergoes. So in the end you probably have to measure your storing needs with a small subset of the expected data and then extrapolate from that. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 13, 2017, 4:46pm UTC](https://discuss.elastic.co/t/compression-factor-in-document-size/74890/3 "2017-03-13T16:46:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.