# VM Appliance Performance Issues

**URL:** <https://community.graylog.org/t/vm-appliance-performance-issues/1999>\
**Category:** Graylog Central (peer support)\
**Created:** [August 8, 2017, 1:11pm UTC](https://community.graylog.org/t/vm-appliance-performance-issues/1999 "2017-08-08T13:11:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ukchris](https://avatars.discourse-cdn.com/v4/letter/u/5f8ce5/32.png) [@ukchris](https://community.graylog.org/u/ukchris)\
**Post date:** [August 8, 2017, 1:11pm UTC](https://community.graylog.org/t/vm-appliance-performance-issues/1999/1 "2017-08-08T13:11:08Z")

</div>

I am using the Ubuntu image, we created a hosted VM based on the appliance with what I think are the same specs the VM had, dual core CPU, 4Gb of RAM. It has been working great but I get the feeling I have abused it and performance has taken a nosedive.

I have been testing the parsing of logs, I have filebeat feeding logs from a folder on my laptop, my process has been to create extractors, feed in some logs (typically up to 6 10mb log files), review the data then delete the index and repeat, adding extractors etc. as I go.

I am up to index graylog\_16 so it’s fair to say I have been through that many iterations, now however the server is slammed, NMON shows one java process using 198% CPU. I have tried restarting graylog (graylog-ctl restart) and rebooting the server but it makes no difference.

I am not concerned about performance overall right now but I would like to know if there’s a way to “reset” things, I’m no expert but I’m guessing it is the journal that is overwhelmed? Without rebuilding the server is there a way to reset everything back, ideally without losing my configuration setup?

Thank,

Chris.

---

<div class="post-metadata">

**Author:** ![ukchris](https://avatars.discourse-cdn.com/v4/letter/u/5f8ce5/32.png) [@ukchris](https://community.graylog.org/u/ukchris)\
**Post date:** [August 8, 2017, 5:42pm UTC](https://community.graylog.org/t/vm-appliance-performance-issues/1999/2 "2017-08-08T17:42:47Z")

</div>

After it running with the CPU maxed out for a day I decided to give **graylog-ctl cleanse** a shot, even after that and a reconfigure the processors are still pegged. I had hoped that would at least reset things even if I had to reconfigure everything again.

Any other suggestions?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [August 22, 2017, 5:42pm UTC](https://community.graylog.org/t/vm-appliance-performance-issues/1999/3 "2017-08-22T17:42:51Z")

</div>

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