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

It's not clear what "hz_actual" represents #211

Open
jontwo opened this issue Feb 6, 2024 · 0 comments
Open

It's not clear what "hz_actual" represents #211

jontwo opened this issue Feb 6, 2024 · 0 comments

Comments

@jontwo
Copy link

jontwo commented Feb 6, 2024

I've just raised a ticket on pytest-benchmark because of differences in the cpuinfo between two test runs.

It looks like hz_actual is just reporting the first value it finds in /proc/cpuinfo, i.e. a snapshot of one core. Would it be possible to take an average or min/max or something more representative? Here's what I see on my machine, the values change every time I run the command.

$ cat /proc/cpuinfo | grep "MHz"
cpu MHz         : 2979.381
cpu MHz         : 1401.886
cpu MHz         : 4000.000
cpu MHz         : 4000.000
cpu MHz         : 2039.271
cpu MHz         : 1797.567
cpu MHz         : 1483.572
cpu MHz         : 4000.000

In your bug report please include:

  • CPU architecture
    Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz

  • Operating System
    NAME="Ubuntu"
    VERSION_ID="22.04"
    VERSION="22.04.3 LTS (Jammy Jellyfish)"

  • Python version
    3.10 (from gitlab's python:3.10 docker image)

  • Version of py-cpuinfo
    9.0.0

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

No branches or pull requests

1 participant