# ElasticSerach Sizing
**URL:** https://discuss.elastic.co/t/elasticserach-sizing/191519
**Category:** Elasticsearch
**Created:** [July 21, 2019, 12:48pm UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519 "2019-07-21T12:48:28Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@akamit225](https://discuss.elastic.co/u/akamit225)
#### Post date: [July 21, 2019, 12:48pm UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/1 "2019-07-21T12:48:28Z")
Hi All,
Please comment on below sizing calculation for 10 days HOT node with 3 years retention period.
Does below calculation is correct.. Please provide your suggestions.
EPS 40000
DOC\_RAW 0.8KB
DOC\_JASON 0.88 KB
Compression Ratio = 30%
DOC\_Indexed size = 0.616 KB
DOC\_Indexed size(with replica) = 1.232 KB
**EPD = 3.965377808 TB**
**HotNode(10 Days) = 39.74033356TB**
**Warm Days[3 years] = 1085**
**Warm storage = 4302.43 TB**
**Calculated Nodes:**
HOT Nodes = 8
Warm Nodes = 258.1460953 (RAM to SSD ratio 1:100)
**Server Configuration**
Cpu = 32 cores
RAM = 128 GB
SSD = 3.75 RAM to SSD ratio 1:30
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 21, 2019, 1:06pm UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/2 "2019-07-21T13:06:05Z")
It is hard to comment on this given that we know nothing about the use case, requirements or what these numbers are based on.
---
### Author:  [@akamit225](https://discuss.elastic.co/u/akamit225)
#### Post date: [July 22, 2019, 12:58am UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/3 "2019-07-22T00:58:26Z")
Hi Christian,
The requirement is to build SIEM solution over ELK stack. Above calculation is done only for ELASTIC SEARCH compute.
Let me know if you need any details.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 22, 2019, 5:03am UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/4 "2019-07-22T05:03:30Z")
How did you arrive at those numbers? Did you do any tests or run any benchmarks? What is the hardware specification you plan to deploy these node types on? How many users will you have? What are the query latency requirements?
I would recommend having a look at the following resources:
[https://www.elastic.co/webinars/elasticsearch-sizing-and-capacity-planning](https://www.elastic.co/webinars/elasticsearch-sizing-and-capacity-planning)
[https://www.elastic.co/webinars/optimizing-storage-efficiency-in-elasticsearch](https://www.elastic.co/webinars/optimizing-storage-efficiency-in-elasticsearch)
> **[How many shards should I have in my Elasticsearch cluster?](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**
>
> If you are looking for practical guidelines around how many indices and shards to have in your cluster, this blog post will help you avoid common pitfalls.
[https://www.elastic.co/blog/sizing-hot-warm-architectures-for-logging-and-metrics-in-the-elasticsearch-service-on-elastic-cloud](https://www.elastic.co/blog/sizing-hot-warm-architectures-for-logging-and-metrics-in-the-elasticsearch-service-on-elastic-cloud)
[https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right)
---
### Author:  [@akamit225](https://discuss.elastic.co/u/akamit225)
#### Post date: [July 22, 2019, 8:12am UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/5 "2019-07-22T08:12:28Z")
I have provided the server and log size details in in initial draft.
User Management will be done by kibana...if I am not wrong.
I believe Query latency depends on processing of es cluster
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 22, 2019, 9:16pm UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/6 "2019-07-22T21:16:04Z")
You have not answered any of my questions from the previous post.
> [@akamit225](#):
>
> DOC\_RAW 0.8KB
> DOC\_JASON 0.88 KB
> Compression Ratio = 30%
> DOC\_Indexed size = 0.616 KB
> DOC\_Indexed size(with replica) = 1.232 KB
Have you run a test to come up with these numbers? If so, did you index at least a few GB? Did you [optimize your mappings](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/tune-for-disk-usage.html)?
> [@akamit225](#):
>
> EPS 40000
Based on the calculation I take it this is an average EPS. If so, what is the expected peak rate the cluster need to be able to keep up with?
> [@akamit225](#):
>
> EPD = 3.965377808 TB
> HotNode(10 Days) = 39.74033356TB
How did you determine that 10 days is the optimal period to keep on the hot nodes. Is this due to query requirements? How did you determine that 8 hot nodes is sufficient?
> [@akamit225](#):
>
> **Calculated Nodes:**
> HOT Nodes = 8
> Warm Nodes = 258.1460953 (RAM to SSD ratio 1:100)
>
> **Server Configuration**
> Cpu = 32 cores
> RAM = 128 GB
> SSD = 3.75 RAM to SSD ratio 1:30
What is the expected specification of the hot nodes? What type of hardware and storage will you be using?
What is the expected specification of the warm nodes? What type of hardware and storage will you be using?
> [@Christian\_Dahlqvist](#):
>
> How many users will you have? What are the query latency requirements?
Here I am looking to see what your users expect and how they will use the cluster. When sizing a cluster it is important to leave enough headroom for querying and not just size the cluster based on the maximum it can index.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 19, 2019, 9:16pm UTC](https://discuss.elastic.co/t/elasticserach-sizing/191519/7 "2019-08-19T21:16:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.