New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable CPU frequency chart #8938
Comments
i see that 50 limitation is hardcoded netdata/collectors/proc.plugin/proc_stat.c Lines 488 to 504 in 77749bb
|
That's not a problem @ilyam8 . The "cores" word is wrong in this document. In reality it's what linux calls "processors" or "CPUs". The computer architecture term would be "hardware threads". If you want to enable all of the options that are automatically disabled due to high processor count in
As a result, you will have more charts, more CPU overhead and more open file descriptors from netdata. |
Thanks for the quick responses!
Ah, right, like I suspected ;)
So it is possible to override this behaviour in the config. Thanks! I have set these options and the charts are working. I'll keep an eye on the performance impact. |
Okay, quick second question: the clock frequency figures I see in the Netdata chart differ from those I obtain from /proc/cpuinfo under load. In Netdata, the frequency doesn't exceed 3.7 Ghz (the CPU's base clock), but using /proc/cpuinfo I see it boosting to about 4.1 GHz. |
It's taken from |
This issue has been mentioned on the Netdata Community Forums. There might be relevant details there: https://community.netdata.cloud/t/enable-cpu-frequency-chart-netdata-cpu-cpufreq/4336/1 |
I want to have the CPU clock frequency chart enabled in Netdata. If I'm not mistaken, this is handled by
proc.plugin
, which is enabled by default. However, my Netdata instance does not have the CPU frequency chart.In the docs I found this statement:
The machine in question has a Threadripper 3970X (32 cores, 64 threads). Is it possible that the threads are counted as 'cores', and that is why the charts are disabled?
Is it possible to turn the charts back on using a config option?
The text was updated successfully, but these errors were encountered: