# Logstash sizing for cores

**URL:** <https://discuss.elastic.co/t/logstash-sizing-for-cores/153957>\
**Category:** Logstash\
**Created:** [October 25, 2018, 9:17am UTC](https://discuss.elastic.co/t/logstash-sizing-for-cores/153957 "2018-10-25T09:17:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\
**Post date:** [October 25, 2018, 9:17am UTC](https://discuss.elastic.co/t/logstash-sizing-for-cores/153957/1 "2018-10-25T09:17:40Z")

</div>

We have a requirement to process 20000 events/second. Logstash uses few GROK filters for event processing. Would like to know how many cores and nodes are required.

---

<div class="post-metadata">

**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:** [October 25, 2018, 10:05am UTC](https://discuss.elastic.co/t/logstash-sizing-for-cores/153957/2 "2018-10-25T10:05:43Z")

</div>

This will depend a lot on the size and complexity of your data and [how well you have optimised your grok filters](https://www.elastic.co/blog/do-you-grok-grok). If you can share your config I am sure you can get some feedback, but I would otherwise recommend running a test with real data to see what throughput you get.

---

<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:** [November 22, 2018, 10:15am UTC](https://discuss.elastic.co/t/logstash-sizing-for-cores/153957/3 "2018-11-22T10:15:46Z")

</div>

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