# ELK Machine capacity for 10000 events per sec

**URL:** <https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818>\
**Category:** Logstash\
**Created:** [August 21, 2015, 7:15am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818 "2015-08-21T07:15:03Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manjunath](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Manjunath](https://discuss.elastic.co/u/Manjunath)\
**Post date:** [August 21, 2015, 7:15am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/1 "2015-08-21T07:15:03Z")

</div>

I have close to 1000 log files which produces 10000 events per sec, out of which i have to extract 1000 events per sec and parse it to elasticsearch.  
Currently i have a machine (bare metal) which has 32 CPU cores, 47 gig RAM.  
What would be the better machine capacity or number of machines for ELK to work ?

Please advice.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 22, 2015, 8:41am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/2 "2015-08-22T08:41:15Z")

</div>

Is your current machine not coping?  
It should be able to cope with that load.

---

<div class="post-metadata">

**Author:** ![Manjunath](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Manjunath](https://discuss.elastic.co/u/Manjunath)\
**Post date:** [August 24, 2015, 11:08am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/3 "2015-08-24T11:08:45Z")

</div>

Well, my groks are taking too much time to process. Thus resulting in a huge latency of processing files.  
I have around 5 logstash config files, and around 1000 files passing to it with /\*.log.  
Each config file has 4 to 6 grok filters.  
Well i really spent lot of time in analysing this without any luck.  
Looks like ES is working fine without much load.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 24, 2015, 11:10am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/4 "2015-08-24T11:10:14Z")

</div>

Then you need to add more LS workers or instances 🙂

---

<div class="post-metadata">

**Author:** ![Manjunath](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Manjunath](https://discuss.elastic.co/u/Manjunath)\
**Post date:** [August 24, 2015, 11:11am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/5 "2015-08-24T11:11:30Z")

</div>

Well i added that too, currently i have 28 workers running. Still resulting in latency.  
Looks like groks are eating up much CPU.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 24, 2015, 11:13am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/6 "2015-08-24T11:13:23Z")

</div>

Maybe we can help tune your grok patterns then?

---

<div class="post-metadata">

**Author:** ![Manjunath](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Manjunath](https://discuss.elastic.co/u/Manjunath)\
**Post date:** [August 24, 2015, 11:17am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/7 "2015-08-24T11:17:54Z")

</div>

That would be really Great 😄.

I am sending the 1st config groks.

```
             "message", "%{TIMESTAMP_ISO8601:log_timestamp}%{DATA}Site %{INT:id}%{DATA}accepted (?<skip>[0-9A-F]{24})(?<sequence_num_hex>[0-9A-F]{8})%{DATA}",
             "message", "%{TIMESTAMP_ISO8601:log_timestamp}%{DATA}Site %{INT}%{DATA}msgid: %{INT:msg_id}%{DATA}track_id: %{INT:track_id}%{DATA}name: %{USERNAME:name}, status: %{WORD:status}",
             "message", "%{TIMESTAMP_ISO8601:log_timestamp}%{DATA}Site %{INT:site}%{DATA}send (?<skip>[0-9A-F]{24})(?<sequence_num_hex>[0-9A-F]{8})%{DATA}",
             "message", "%{TIMESTAMP_ISO8601:log_timestamp}%{DATA}Site %{INT:site}%{DATA}msgid %{INT:msg_id}%{DATA}sdu: %{INT} %{INT} %{INT} %{INT:num}"
```

---

<div class="post-metadata">

**Author:** ![Manjunath](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Manjunath](https://discuss.elastic.co/u/Manjunath)\
**Post date:** [August 25, 2015, 12:33pm UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/8 "2015-08-25T12:33:22Z")

</div>

does the groks looks fine, its eating up lot of CPU.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 1, 2015, 7:56am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/9 "2015-09-01T07:56:47Z")

</div>

I'd try creating custom patterns for the regex stuff you have in there, and then drop them using mutate (if that is what you are doing).

---

<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:** [July 6, 2017, 5:30am UTC](https://discuss.elastic.co/t/elk-machine-capacity-for-10000-events-per-sec/27818/10 "2017-07-06T05:30:33Z")

</div>