High CPU from go.d/logind #16709
Unanswered
TheOldMan2000
asked this question in
Q&A
Replies: 2 comments 8 replies
-
Hi. Your screenshot doesn't say much, I think you will need to debug it yourself:
There is only one known issue - go.d/ping in privileged mode (default). |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @ilyam8 |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I recently came back to Netdata after a while away and am loving all the improvements. I've noticed that Netdata is using about 56% constant CPU resources, which isn't so great. Specifically, it seems to be the Go.d plugin/collector. I'm running the latest v1.44.0-122-nightly version on Alma Linux 8 (Virtuozzo) with 8 CPU cores and 8GB RAM. I tried switching off the Machine Learning and it made no difference (screenshot attached). The Netdata set-up is almost stock, aside from adding the login details for several Redis pool instances. Is it a known issue at the moment?
The other thing I've noticed is that whereas before I could use Netdata on my iPad (128MB 2017 model) and could scroll several pages down before it white screened, now it is just a few charts. So I wondered if you had any plans for an App at all?
Many thanks.
Beta Was this translation helpful? Give feedback.
All reactions