# Hardware requirement ELK **URL:** \ **Category:** Elasticsearch\ **Created:** [September 24, 2019, 8:56pm UTC](https://discuss.elastic.co/t/hardware-requirement-elk/200934 "2019-09-24T20:56:56Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [September 24, 2019, 9:25pm UTC](https://discuss.elastic.co/t/hardware-requirement-elk/200934/2 "2019-09-24T21:25:59Z")
If we make the simplified assumption that your index data on disk take up the same amount of space as the raw data and that you will have a replica for high availability we get 1.2TB of indices generated per day. Over 90 days this is over 100 TB of data. Given that I would expect you to need considerably more than 3 Elasticsearch nodes. If we were to assume that each node can handle e.g. 5TB if data you would need around 20 nodes. Whether this is a high or low estimate will depend on your hardware and performance requirements. The amount of data a node can handle is usually driven by query latency requirements or heap usage. You can have a look at [this webinar](https://www.elastic.co/webinars/optimizing-storage-efficiency-in-elasticsearch) for a discussion around this. To optimize and reduce the size you indices take up on disk and ensure you do better than the simplified assumption used above I would recommend [looking at this section in the docs](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/tune-for-disk-usage.html). --- _[View the full topic](https://discuss.elastic.co/t/hardware-requirement-elk/200934)._