# Do shards use separate processors on single node? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 13, 2016, 5:33pm UTC](https://discuss.elastic.co/t/do-shards-use-separate-processors-on-single-node/55432 "2016-07-13T17:33:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ChrisR](https://avatars.discourse-cdn.com/v4/letter/c/ecd19e/32.png) [@ChrisR](https://discuss.elastic.co/u/ChrisR)\ **Post date:** [July 13, 2016, 5:33pm UTC](https://discuss.elastic.co/t/do-shards-use-separate-processors-on-single-node/55432/1 "2016-07-13T17:33:59Z")
For general awareness, do separate shards on a single node use separate processors? Do the shards use separate cores but only a single processor? Is the behavior different between windows and linux? I ask because when I start up a single-node, multi-shard instance on windows, I see only one new process in Task Manager. Even after executing a query, I don't see any more processes. On linux, I see only a single process for a single-node, multi-shard instance. ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [July 13, 2016, 5:50pm UTC](https://discuss.elastic.co/t/do-shards-use-separate-processors-on-single-node/55432/2 "2016-07-13T17:50:15Z")
There will be only one process per server. Each JVM instance runs multiple threads per process, which are constrained by the thread pools: [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-threadpool.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-threadpool.html) The number of shards has no relevance on the number of threads. Each shard is a separate Lucene index, but they are all managed by the cluster. Ivan ---
**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, 10:35pm UTC](https://discuss.elastic.co/t/do-shards-use-separate-processors-on-single-node/55432/3 "2017-07-05T22:35:56Z")