# Running multiple instances of Elasticsearch on the same host - Allocated processors setting

**URL:** <https://discuss.elastic.co/t/running-multiple-instances-of-elasticsearch-on-the-same-host-allocated-processors-setting/362372>\
**Category:** Elasticsearch\
**Created:** [July 2, 2024, 10:50am UTC](https://discuss.elastic.co/t/running-multiple-instances-of-elasticsearch-on-the-same-host-allocated-processors-setting/362372 "2024-07-02T10:50:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![avnere](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@avnere](https://discuss.elastic.co/u/avnere)\
**Post date:** [July 2, 2024, 10:50am UTC](https://discuss.elastic.co/t/running-multiple-instances-of-elasticsearch-on-the-same-host-allocated-processors-setting/362372/1 "2024-07-02T10:50:44Z")

</div>

Hi,

I have machine with 86 cores and I want to run multiple instances of Elasticsearch on it.  
I want to isolate the number of cores foreach node.

I saw in [multiple instances of Elasticsearch on the same host]( [Thread pools | Elasticsearch Guide [8.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html#node.processors) that it is possible be setting node.processors in yml.  
However also mentioned

> setting the `node.processors` setting as there are other considerations like changing the number of garbage collector threads, pinning processes to cores, and so on.

What does it mean? What else need to be done?

Thanks...