# Correct Sizing and compression on Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [November 13, 2020, 1:45pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349 "2020-11-13T13:45:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![xziten](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xziten/32/76885_2.png) [@xziten](https://discuss.elastic.co/u/xziten)\ **Post date:** [November 13, 2020, 1:45pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/1 "2020-11-13T13:45:51Z")
Hi, I am trying to get some ratio about Elasticsearch cluster. I have this base : ``` **For 100 Gb of raw data / day :** * 110 Gb of data are indexed (~ +10% for datatype) * 220 Gb with 1 replica * 6600 Gb per month * +15% disk space to avoid saturation (7590 Gb) Disk space with Hot/Warm architecture: * Hot Data Node : Disk/RAM Ratio 30:1 * Warm Data Node : Disk/RAM Ratio 100:1 * 3 Masters Nodes with limited sizing ``` The fact is I think that I am wrong. That's a lot of Gb for a database. Does Elastic apply any compression ? Do u have some ratio to give me. Thanks ---
**Author:** ![abrx](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abrx/32/43881_2.png) [@abrx](https://discuss.elastic.co/u/abrx)\ **Post date:** [November 13, 2020, 2:53pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/2 "2020-11-13T14:53:15Z")
Hi, Not answering the question, but don't forget to [force merge](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-forcemerge.html) indices (with flush enabled, in 1 segment) that are read-only to add some optimization in size (flush really delete deleted documents) and query time (less Lucene segment to look on) 🙂 ---
**Author:** ![xziten](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xziten/32/76885_2.png) [@xziten](https://discuss.elastic.co/u/xziten)\ **Post date:** [November 13, 2020, 8:16pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/3 "2020-11-13T20:16:31Z")
Hi, thank you for your answer, I will notice it 🙂 ---
**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\ **Post date:** [November 13, 2020, 8:30pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/4 "2020-11-13T20:30:31Z")
A few things that you also might want to look into: 1. Index setting: codec, you can set to best\_compression which compresses the \_source more, saving additional space. [https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html) 2. For historical stuff, you can look into searchable snapshots which were added in 7.10. This allows you to have offload the replica to an S3 bucket, and in the event the primary shard goes down, Elasticsearch will automatically start a restore of the snapshot to an available node. This saves on having to keep replicas for older data. [https://www.elastic.co/blog/introducing-elasticsearch-searchable-snapshots](https://www.elastic.co/blog/introducing-elasticsearch-searchable-snapshots) ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 13, 2020, 8:54pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/5 "2020-11-13T20:54:36Z")
I would recommend reading [this section in the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/tune-for-disk-usage.html). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 11, 2020, 8:54pm UTC](https://discuss.elastic.co/t/correct-sizing-and-compression-on-elasticsearch/255349/6 "2020-12-11T20:54:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.