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
[macOS] CPU utilization contains zeroes #2368
Comments
What does htop or similar tools show? 0.1 is a small interval. Task manager tools usually use 1 sec instead. What happens if you use 1 sec? |
htop works fine. You can just let it run with 100ms resolution and the many consecutive "0" values do not occur. For clarification: These values do occuer always no matter what kind of load we are running. So even if all cores are fully stressed zeros creep in, which is probably due to the used syscall. We have actually created working code for one our tools. Please find it here: https://github.com/green-coding-solutions/green-metrics-tool/blob/main/metric_providers/cpu/utilization/mach/system/source.c We are using See also discussion here: green-coding-solutions/green-metrics-tool#330 |
@ribalba FYI |
I wrote a blog article about the problem here: |
Nice finding! It's kind of shocking that CPU metrics on macOS have been wrong for so long and nobody noticed. |
To be fair, it is unknown exactly in which version of macOS this isse happens and if it also is on all chip.s @ribalba and I both have M1 machines. Untested on Intel and M2. We are happy to provide a PR and some tests for macOS that test this feature (Stressing a core and seeing if zeros still exist in output), but I see that this repo currently has no macOS Github Actions runner defined. If we provide a PR, does this repo have the possiblity to have a macOS Runner running that can test the CPU Utilization? |
We currently have CI runners for macOS x86-64 and arm (this one was added yesterday). |
Summary
Description
I searched for utilization and could not find anything that matches this, so I hope it is not a dup.
When using
psutil.cpu_percent(0.1)
on my macOS while running a constant stress in parallel (stress-ng -c 1
) I get a lot of zeros in between.The same behaviour is also when I increase the stress to more cores. Say 8
The same behaviour does not happen on linux machines.
The text was updated successfully, but these errors were encountered: