# Scaling ElasticSearch Vertically

**URL:** <https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772>\
**Category:** Elasticsearch\
**Created:** [January 21, 2016, 1:24pm UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772 "2016-01-21T13:24:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulnadella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahulnadella/32/22117_2.png) [@rahulnadella](https://discuss.elastic.co/u/rahulnadella)\
**Post date:** [January 21, 2016, 1:24pm UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772/1 "2016-01-21T13:24:11Z")

</div>

Our team plans to scale our ElasticSearch cluster vertically.

I was wondering what optimal configuration of the cluster would be best for us (for instance the number of nodes, number of shards and replicas)?

Our current system specs are 2.6 GHz with 20 cores, 132 GB RAM, and 10 TB drive. Current size of indexes per day are between 40 GB and 200 GB.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 22, 2016, 4:01am UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772/2 "2016-01-22T04:01:19Z")

</div>

There's not much point in this, the heap should really only be 30GB.

---

<div class="post-metadata">

**Author:** ![rahulnadella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahulnadella/32/22117_2.png) [@rahulnadella](https://discuss.elastic.co/u/rahulnadella)\
**Post date:** [January 22, 2016, 4:10pm UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772/3 "2016-01-22T16:10:36Z")

</div>

Basically I have multiple instances running to take advantage of the memory, so basically I have 3 instances currently running on the same box talking to each other. Since Logstash is indexing data at large amounts per day, I was wondering if adding more instances would benefit performance on search the data in ElasticSearch?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 22, 2016, 7:21pm UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772/4 "2016-01-22T19:21:32Z")

</div>

Possibly/probably, you'd have to check based on your use case and the specs of your hardware.

---

<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, 11:22pm UTC](https://discuss.elastic.co/t/scaling-elasticsearch-vertically/39772/5 "2017-07-05T23:22:14Z")

</div>