Skip to content
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

Open
ArneTR opened this issue Feb 5, 2024 · 7 comments
Open

[macOS] CPU utilization contains zeroes #2368

ArneTR opened this issue Feb 5, 2024 · 7 comments

Comments

@ArneTR
Copy link

ArneTR commented Feb 5, 2024

Summary

  • OS: macOS 13.6.3 (22G436)
  • Architecture: ARM
  • Psutil version: 5.9.8
  • Python version: 3.10.13
  • Type: core

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.

Screenshot 2024-02-05 at 10 38 33 AM

The same behaviour is also when I increase the stress to more cores. Say 8

>>> while True: psutil.cpu_percent(0.1)
...
100.0
100.0
100.0
100.0
0.0
0.0
0.0
0.0
0.0

The same behaviour does not happen on linux machines.

@ArneTR ArneTR added the bug label Feb 5, 2024
@ArneTR ArneTR changed the title [OS] title [macOS] CPU utilization contains zeroes Feb 5, 2024
@github-actions github-actions bot added the macos label Feb 5, 2024
@giampaolo
Copy link
Owner

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?

@ArneTR
Copy link
Author

ArneTR commented Mar 15, 2024

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 host_processor_info and not host_statistics.

See also discussion here: green-coding-solutions/green-metrics-tool#330

@ArneTR
Copy link
Author

ArneTR commented Mar 15, 2024

@ribalba FYI

@ribalba
Copy link

ribalba commented Mar 15, 2024

I wrote a blog article about the problem here:

https://www.green-coding.io/blog/cpu-utilization-mac/

@giampaolo
Copy link
Owner

giampaolo commented Mar 15, 2024

Nice finding! It's kind of shocking that CPU metrics on macOS have been wrong for so long and nobody noticed.

@ArneTR
Copy link
Author

ArneTR commented Mar 16, 2024

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?

@giampaolo
Copy link
Owner

We currently have CI runners for macOS x86-64 and arm (this one was added yesterday).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants