# Filebeat cpu high

**URL:** <https://community.graylog.org/t/filebeat-cpu-high/10110>\
**Category:** Graylog Central (peer support)\
**Created:** [April 25, 2019, 12:56am UTC](https://community.graylog.org/t/filebeat-cpu-high/10110 "2019-04-25T00:56:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xuziheng1002](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/xuziheng1002/32/446_2.png) [@xuziheng1002](https://community.graylog.org/u/xuziheng1002)\
**Post date:** [April 25, 2019, 12:56am UTC](https://community.graylog.org/t/filebeat-cpu-high/10110/1 "2019-04-25T00:56:26Z")

</div>

when large logs collector to graylog-server by filebeat. it will cost doubule resource of CPU, as below picture:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/c/cac8cf73a6da74481404432166b84a3682c6d0b6.png)  
any way to resolve this issue？ any way to limit the max-useage of cpu/memory?

---

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [April 29, 2019, 6:27am UTC](https://community.graylog.org/t/filebeat-cpu-high/10110/2 "2019-04-29T06:27:29Z")

</div>

reduce the normalisation of logs would be the only that came to my mind … because processing messages eats ressources.

---

<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:** [May 13, 2019, 6:27am UTC](https://community.graylog.org/t/filebeat-cpu-high/10110/3 "2019-05-13T06:27:30Z")

</div>

Closed on May 13, 2019, 6:27am UTC

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