# Constant high cpu usage from Filebeat **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [February 12, 2019, 12:22pm UTC](https://discuss.elastic.co/t/constant-high-cpu-usage-from-filebeat/168028 "2019-02-12T12:22:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![nskerl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nskerl/32/40847_2.png) [@nskerl](https://discuss.elastic.co/u/nskerl)\ **Post date:** [February 12, 2019, 6:00pm UTC](https://discuss.elastic.co/t/constant-high-cpu-usage-from-filebeat/168028/2 "2019-02-12T18:00:44Z")
Just wanted to ref my own issue here, as I saw a very similar CPU pattern with a high number of `current` files. I see the same in your output. I was able to resolve my CPU issue by reducing the number of _stale_ files in the registry, but I still don't understand why that helped. > [@Log file size vs. quantity](https://discuss.elastic.co/t/log-file-size-vs-quantity/168090): > > While troubleshooting high cpu usage by Filebeat (80% sustained, even when logs are idle), I noticed it showed a large number of files (current: 8811) in the registrar: "harvester":{"open\_files":4,"running":4}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"acked":214,"batches":4,"total":214},"read":{"bytes":24},"write":{"bytes":16075}},"pipeline":{"clients":1,"events":{"active":0,"published":214,"total":214},"queue":{"acked":214}}},"registrar":{"states":{"current":8811,"upda… --- _[View the full topic](https://discuss.elastic.co/t/constant-high-cpu-usage-from-filebeat/168028)._