# Optimizing a single node ES instance for throughput

**URL:** https://discuss.elastic.co/t/optimizing-a-single-node-es-instance-for-throughput/307808
**Category:** Elasticsearch
**Created:** [June 21, 2022, 10:22pm UTC](https://discuss.elastic.co/t/optimizing-a-single-node-es-instance-for-throughput/307808 "2022-06-21T22:22:05Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![sandeepkanabar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandeepkanabar/32/79399_2.png) [@sandeepkanabar](https://discuss.elastic.co/u/sandeepkanabar)
#### Post date: [June 30, 2022, 6:20am UTC](https://discuss.elastic.co/t/optimizing-a-single-node-es-instance-for-throughput/307808/5 "2022-06-30T06:20:46Z")

</div>

> [@dmh43](#):
>
> I have a single large (500GB ram

Because the max recommended ES heap size is 32 GB. See this - [Use more than 32GB for heap - #2 by spinscale](https://discuss.elastic.co/t/use-more-than-32gb-for-heap/204422/2). So in effect, you aren't able to fully utilise the full RAM.

So you can either set up multiple instances or you can set-up multiple VM (nodes). cost-wise it would actually work out lesser for you.

Also have a look at [Managing and troubleshooting Elasticsearch memory | Elastic Blog](https://www.elastic.co/blog/managing-and-troubleshooting-elasticsearch-memory)

---

_[View the full topic](https://discuss.elastic.co/t/optimizing-a-single-node-es-instance-for-throughput/307808)._