# Transport Client Thread Pool Size **URL:** \ **Category:** Elasticsearch\ **Created:** [January 7, 2016, 2:07pm UTC](https://discuss.elastic.co/t/transport-client-thread-pool-size/38624 "2016-01-07T14:07:40Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![petemcc](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@petemcc](https://discuss.elastic.co/u/petemcc)\ **Post date:** [January 7, 2016, 2:07pm UTC](https://discuss.elastic.co/t/transport-client-thread-pool-size/38624/1 "2016-01-07T14:07:40Z")
We are using the Java transport client which is creating a thread pool of a size that appears to be based on available processors. We have a search intensive application (i.e. thousands of searches make up a single operation) that seems to be bottlenecking based on the thread pool size. I can understand having a thread pool size based on the processor count for a CPU intensive operation...but this isn't CPU intensive, it's basically the client waiting for remote ES searches to complete - so I expect we can achieve performance gains by conducting a larger number of simultaneous searches than the processor count on our client machine. Is there a way for us to adjust the transport client thread pool size? Thanks. ---
**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:26pm UTC](https://discuss.elastic.co/t/transport-client-thread-pool-size/38624/2 "2017-07-05T23:26:22Z")