# Need opinion on deploying es on a server

**URL:** <https://discuss.elastic.co/t/need-opinion-on-deploying-es-on-a-server/48218>\
**Category:** Elasticsearch\
**Created:** [April 23, 2016, 7:03am UTC](https://discuss.elastic.co/t/need-opinion-on-deploying-es-on-a-server/48218 "2016-04-23T07:03:22Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Bruce\_Ritchie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_ritchie/32/9370_2.png) [@Bruce\_Ritchie](https://discuss.elastic.co/u/Bruce_Ritchie)\
**Post date:** [April 23, 2016, 1:50pm UTC](https://discuss.elastic.co/t/need-opinion-on-deploying-es-on-a-server/48218/5 "2016-04-23T13:50:43Z")

</div>

64Gb of memory isn't all that much once you take into account FS cache with a decent sized index. I wouldn't recommend doing multi nodes on such a server - rather just do a bit of tuning and spread the I/O across multiple disks if you can.

I'm actually looking at doing option #3 but only because I have one very large machine (512Gb mem, 32 cores, etc) to work with. It's not what I would term as ideal but it's what I have to work with. This doc ([Can I run multiple Elasticsearch nodes on the same machine?](https://discuss.elastic.co/t/can-i-run-multiple-elaticsearch-nodes-on-the-same-machine/67)) does a great job of describing how to accomplish it.

---

_[View the full topic](https://discuss.elastic.co/t/need-opinion-on-deploying-es-on-a-server/48218)._