# Logstash Using a lot of CPU

**URL:** <https://discuss.elastic.co/t/logstash-using-a-lot-of-cpu/95214>\
**Category:** Logstash\
**Created:** [July 31, 2017, 3:44pm UTC](https://discuss.elastic.co/t/logstash-using-a-lot-of-cpu/95214 "2017-07-31T15:44:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Warren\_Turner](https://avatars.discourse-cdn.com/v4/letter/w/e9c0ed/32.png) [@Warren\_Turner](https://discuss.elastic.co/u/Warren_Turner)\
**Post date:** [July 31, 2017, 3:44pm UTC](https://discuss.elastic.co/t/logstash-using-a-lot-of-cpu/95214/1 "2017-07-31T15:44:27Z")

</div>

Hey guys, I'm having an issue where logstash uses 5 CPU cores even when there is no configs.

I'm running version 5.5.1 on Ubuntu 16.04. I tried increasing the JVM heap size (recommended in the performance troubleshooting guide) but that didn't seem to have any effect. I could understand if I was doing some sort of complex transform but logstash it literally just turning on and off checking for streams. Any ideas?

---

<div class="post-metadata">

**Author:** ![Warren\_Turner](https://avatars.discourse-cdn.com/v4/letter/w/e9c0ed/32.png) [@Warren\_Turner](https://discuss.elastic.co/u/Warren_Turner)\
**Post date:** [July 31, 2017, 5:08pm UTC](https://discuss.elastic.co/t/logstash-using-a-lot-of-cpu/95214/2 "2017-07-31T17:08:33Z")

</div>

Well how about that, I figured this out a few hours after I posted this. The issue was that when there are no config files, logstash starts and then crashes and then tries to start again (repeat forever). While starting logstash uses a lot of CPU to start the pipeline, thus looking like it was constantly using a bunch.

---

<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:** [August 28, 2017, 5:08pm UTC](https://discuss.elastic.co/t/logstash-using-a-lot-of-cpu/95214/3 "2017-08-28T17:08:43Z")

</div>

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