# ELK, DImensioning trouble and doubts **URL:** \ **Category:** Elasticsearch\ **Created:** [October 25, 2017, 8:05pm UTC](https://discuss.elastic.co/t/elk-dimensioning-trouble-and-doubts/105291 "2017-10-25T20:05:38Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![agonex](https://avatars.discourse-cdn.com/v4/letter/a/e9c0ed/32.png) [@agonex](https://discuss.elastic.co/u/agonex)\ **Post date:** [October 25, 2017, 8:05pm UTC](https://discuss.elastic.co/t/elk-dimensioning-trouble-and-doubts/105291/1 "2017-10-25T20:05:39Z")
We need to know more about how dimensioning the ELK cluster because the performance is too badly, make a search in kibana is not possible,very slowly any consult result in timeout also JVM logs indicate OutOfMemory.. , in this moment we have a production cluster with next conditions: 3 Physical hosts to ES 12 Gb RAM and / or, 5 core CPU and / or, 2.5TB e/o 3 Master Nodes 5gb e/o 3 Slaves Nodes 5gb e/o Heap Size to master nodes: 2gb each Heap Size slave nodes: 2gb each Kibana and Logtash independient hosts 1 cordinator node ES running in Kibana and Logtash server We have a 5 shards and 1 replica Documents by day: 2,700,000 Space in disk by day: 37gb Weigth of each document: 14kb We are planning a physical upgrade and redimensioning cluster ELK to get better performance in cluster, we are thinking getting up RAM Slave Nodes to 14gb RAM and 7gb Heapsize... We don have any idea about how much shards and replica we need with that amount of data.. Thanks in Advance, If Needs another info just tell us... ---
**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:** [October 25, 2017, 8:34pm UTC](https://discuss.elastic.co/t/elk-dimensioning-trouble-and-doubts/105291/2 "2017-10-25T20:34:53Z")
I would recommend that read [this blog post for some practical guidelines on sharding](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster). Then install montering so you can see what is limiting performance and causing issues. You may also benefit from [this talk](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing) and [this guide](https://www.elastic.co/guide/en/elasticsearch/guide/current/deploy.html). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 22, 2017, 8:35pm UTC](https://discuss.elastic.co/t/elk-dimensioning-trouble-and-doubts/105291/3 "2017-11-22T20:35:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.