# ElasticSearch threadpool and thread count

**URL:** <https://discuss.elastic.co/t/elasticsearch-threadpool-and-thread-count/9098>\
**Category:** Elasticsearch\
**Created:** [September 21, 2012, 3:34pm UTC](https://discuss.elastic.co/t/elasticsearch-threadpool-and-thread-count/9098 "2012-09-21T15:34:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Philippe\_Vaucher](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@Philippe\_Vaucher](https://discuss.elastic.co/u/Philippe_Vaucher)\
**Post date:** [September 21, 2012, 3:34pm UTC](https://discuss.elastic.co/t/elasticsearch-threadpool-and-thread-count/9098/1 "2012-09-21T15:34:27Z")

</div>

Hello,

Here's my threadpool configuration (test conf):

[https://gist.github.com/3762162](https://gist.github.com/3762162)

And here's the stats elasticsearch:

[https://gist.github.com/3762104](https://gist.github.com/3762104)

We can see that "threads:" is 37, but in the "thread\_pool" part we see that  
only 7 are supposed to be used.

My question is, from where comes such a big difference? Is that all the  
Network/Filesystem IO background threads from the JVM?

I have to run elasticsearch on a machine that only uses 512Mb of RAM (no  
clusterization, only one server for the app). I reduced the number of  
shards to 1 and set replica to 0 to save what I can in terms of memory, but  
it seems that limiting the number of threads in each threadpool is a dead  
end reguarding saving memory.

Philippe

--

---

<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 6, 2017, 3:11am UTC](https://discuss.elastic.co/t/elasticsearch-threadpool-and-thread-count/9098/2 "2017-07-06T03:11:56Z")

</div>