# Volume Sizing Example **URL:** \ **Category:** Elasticsearch\ **Created:** [November 18, 2019, 5:07pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357 "2019-11-18T17:07:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![magneton](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@magneton](https://discuss.elastic.co/u/magneton)\ **Post date:** [November 18, 2019, 5:07pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357/1 "2019-11-18T17:07:39Z")
Dear Elastic In your webinar, you gave the following formula for volume sizing: ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/4/e4c4d10af6192e8ef47af2771ba9da23618fb0e1.png) I want to just check with a worked example. so for 1.5TB retained for 7 days with one replica Total Data = 1.5 \*7 \*2 = 22TB. Total Storage = 22 TB \*1.20 = 26.4TB Nodes have 64GB ram, Total Data Nodes = 26400 /64 / 30 = 13.75 +1 = 15 nodes. Here is my question that was not clear in the slide, the ideal memory:data ratio was shown to be 1:30 for a hot node and was explained that the maximum storage per node was 64 x 30 = 1920 GB or 1.92 TB. What happens if I increase storage to have fewer nodes for example what if I only had three nodes with 26.4TB of storage compared to 15 nodes of 1.92 TB what would be the effect? Could someone please clarify, the memory:data ratio portion of the calculation in the example above for me? Kind Regards Magneton ---
**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 18, 2019, 5:56pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357/2 "2019-11-18T17:56:49Z")
Each node has a certain amount of resources available, e.g. CPU, heap space and disk I/O capacity. Indexing, querying as well as just storing data use resources, and therefore compete for resources with eachother. Indexing is a very disk I/O intensive process but can also use a lot of CPU and need a good amount of heap space as well. Querying also uses the same resources and the amount of resources required depend on the required query latency as well as the amount of data queried. Just storing data on a node typically just consume heap. > [@magneton](#): > > Here is my question that was not clear in the slide, the ideal memory:data ratio was shown to be 1:30 for a hot node and was explained that the maximum storage per node was 64 x 30 = 1920 GB or 1.92 TB. This is based on empirical observations and is what a lot of users use for hot nodes. Holding relatively little data means querying and storage require less resources, which leaves more for indexing. It is all about finding a good balance between indexing, storage and querying. > [@magneton](#): > > What happens if I increase storage to have fewer nodes for example what if I only had three nodes with 26.4TB of storage compared to 15 nodes of 1.92 TB what would be the effect? If you have 3 nodes instead of 15, each node will need to index 5 times as much. They will also store 5 times as much data and handle querying for 5 times the data volume. At the ingest volumes and retention period you mentioned I suspect you will run into resource limitations at a very early stage. You can also have a look at [this webinar](https://www.elastic.co/webinars/optimizing-storage-efficiency-in-elasticsearch), which talks about heap usage and how to optimize it. ---
**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 18, 2019, 6:23pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357/4 "2019-11-18T18:23:35Z")
Yes, the ratio is often given relative the total RAM available to the node, assuming 50% is given to heap, which in practice generally means at most 64GB RAM. [This blog post](https://www.elastic.co/blog/sizing-hot-warm-architectures-for-logging-and-metrics-in-the-elasticsearch-service-on-elastic-cloud) might also be useful. ---
**Author:** ![magneton](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@magneton](https://discuss.elastic.co/u/magneton)\ **Post date:** [November 19, 2019, 12:04pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357/5 "2019-11-19T12:04:08Z")
Cheers Christian ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 17, 2019, 12:04pm UTC](https://discuss.elastic.co/t/volume-sizing-example/208357/6 "2019-12-17T12:04:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.