# Logstash Performance

**URL:** https://discuss.elastic.co/t/logstash-performance/298942
**Category:** Logstash
**Created:** [March 7, 2022, 8:46am UTC](https://discuss.elastic.co/t/logstash-performance/298942 "2022-03-07T08:46:41Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![mani1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mani1/32/91044_2.png) [@mani1](https://discuss.elastic.co/u/mani1)
#### Post date: [March 7, 2022, 8:46am UTC](https://discuss.elastic.co/t/logstash-performance/298942/1 "2022-03-07T08:46:41Z")

</div>

Hello ,  
We have maximize the Logstash performance in terms of processed events per sec, by tuning vcpus, Heap, pipeline workers, Consumer Threads, N/w bandwidth, Batch size etc. There is no scarcity of resources assigned to Logstash application which is running on a VM machine. The Logstash  
is reading from Kafka Topic and writing to Elastic Cluster Hot node via Coordination Nodes. We also tuned Topic partitions.

```
        I wanted to know whether any other point is available which can improve the Logstash

```

performance, e.g. CPU Pining, socket sharding, Kernel bypass etc. Are these features supported by Logstash and will improve it’s performance. Any feedback on this will be quite helpful.

---

<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: [April 4, 2022, 8:47am UTC](https://discuss.elastic.co/t/logstash-performance/298942/2 "2022-04-04T08:47:13Z")

</div>

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