# Ingest Pipeline threads **URL:** \ **Category:** Elasticsearch\ **Created:** [September 26, 2022, 3:00pm UTC](https://discuss.elastic.co/t/ingest-pipeline-threads/315182 "2022-09-26T15:00:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![alah64](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alah64/32/100065_2.png) [@alah64](https://discuss.elastic.co/u/alah64)\ **Post date:** [September 26, 2022, 3:00pm UTC](https://discuss.elastic.co/t/ingest-pipeline-threads/315182/1 "2022-09-26T15:00:58Z")
In logstash, the pipeline.workers setting determines how many threads to run to process the filter and output. Do we have similar settings for elasticsearch ingest pipeline? It seems to work single-threaded and the more processes we create the slower the number of processing of all events, even those that will be in another pipeline, is this correct? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 30, 2022, 3:57am UTC](https://discuss.elastic.co/t/ingest-pipeline-threads/315182/2 "2022-09-30T03:57:38Z")
I believe each bulk request is processed in a single thread, but different bulk requests can be processed in parallel. The number of bulk requests that can be processed in parallel is driven by the size of the supporting thread pool, which is generally proportional to the number of available CPU cores on the node. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 28, 2022, 3:58am UTC](https://discuss.elastic.co/t/ingest-pipeline-threads/315182/3 "2022-10-28T03:58:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.