# Elasticsearch client nodes

**URL:** <https://discuss.elastic.co/t/elasticsearch-client-nodes/26598>\
**Category:** Elasticsearch\
**Created:** [July 30, 2015, 10:24pm UTC](https://discuss.elastic.co/t/elasticsearch-client-nodes/26598 "2015-07-30T22:24:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AGirin](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@AGirin](https://discuss.elastic.co/u/AGirin)\
**Post date:** [July 30, 2015, 10:24pm UTC](https://discuss.elastic.co/t/elasticsearch-client-nodes/26598/1 "2015-07-30T22:24:22Z")

</div>

Hi!

We are trying to see if we can introduce client nodes into our Elasticsearch cluster. I have yet to find any recommendations as far as memory requirements and Java settings for client nodes. Do they follow the same principles as data nodes? 50% of ram to heap and 50% to OS (not to exceed 32gb though)?

What about CPU? Is it preferable to have a lot of cores for client nodes?

Your insight is greatly appreciated!

Andrew

---

<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:** [July 30, 2015, 11:00pm UTC](https://discuss.elastic.co/t/elasticsearch-client-nodes/26598/2 "2015-07-30T23:00:49Z")

</div>

You can easily increase heap on client nodes to 75% as you don't have to worry about FS caching to speed things up.  
However don't go over the 30.5GB limit 😄

As for CPU, whatever you can give it!

---

<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:58pm UTC](https://discuss.elastic.co/t/elasticsearch-client-nodes/26598/3 "2017-07-05T23:58:04Z")

</div>