# Elastic search server configuration

**URL:** <https://discuss.elastic.co/t/elastic-search-server-configuration/51630>\
**Category:** Elasticsearch\
**Created:** [June 1, 2016, 11:36pm UTC](https://discuss.elastic.co/t/elastic-search-server-configuration/51630 "2016-06-01T23:36:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sreejith](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@sreejith](https://discuss.elastic.co/u/sreejith)\
**Post date:** [June 1, 2016, 11:36pm UTC](https://discuss.elastic.co/t/elastic-search-server-configuration/51630/1 "2016-06-01T23:36:36Z")

</div>

, could you please let us know the elastic server configuration required based on the below details

1. Daily log volume shipping to elastic search average is 10-15 G , so average index size is ~30 G with 2 shards

2. Current configuration with 2 elastic search node is  
a. 8x16 G Ram  
b. 500 G storage

We have tried the doc\_value option to resolve the memory issue , seems its impacting the performance of visualization creation . Instead of making this change in production requesting your assistance on setting up correct server infrastructure to avoid further issue

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:47pm UTC](https://discuss.elastic.co/t/elastic-search-server-configuration/51630/2 "2017-07-05T22:47:06Z")

</div>

Closed on July 5, 2017, 10:47pm UTC