# Logstash tuning w/ 35 pipelines

**URL:** <https://discuss.elastic.co/t/logstash-tuning-w-35-pipelines/285345>\
**Category:** Logstash\
**Created:** [September 28, 2021, 11:12am UTC](https://discuss.elastic.co/t/logstash-tuning-w-35-pipelines/285345 "2021-09-28T11:12:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkward](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pkward/32/95305_2.png) [@pkward](https://discuss.elastic.co/u/pkward)\
**Post date:** [September 28, 2021, 11:12am UTC](https://discuss.elastic.co/t/logstash-tuning-w-35-pipelines/285345/1 "2021-09-28T11:12:39Z")

</div>

Hi,

I have an Elasticsearch cluster with 24 data nodes. I have about 35 logstash pipelines on a single server that has 4 CPUs and 16 GB RAM. Each Logstash pipeline has 18 filters w/ two of them being Elasticsearch filters for lookups. Is there a minimum hardware spec or best practice for this kind of work load? I've upgraded the EC2 instance to have 8 CPUs and 32GB RAM, but it still seems to utilize 400% of CPU. We're planning to load balance to multiple Logstash servers, but I'm in need of a quick fix for now.

---

<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:** [October 26, 2021, 11:12am UTC](https://discuss.elastic.co/t/logstash-tuning-w-35-pipelines/285345/2 "2021-10-26T11:12:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.