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

consistency of CPU time units #66

Closed
heckj opened this issue Feb 26, 2023 · 0 comments · Fixed by #76
Closed

consistency of CPU time units #66

heckj opened this issue Feb 26, 2023 · 0 comments · Fixed by #76

Comments

@heckj
Copy link
Contributor

heckj commented Feb 26, 2023

Exploring benchmarks, I was exploring setting
Benchmark.defaultConfiguration.timeUnits = .microseconds. It does exactly what it says for the metric Time (wall clock), but doesn't appear to do anything with Time (system CPU) (μs), Time (total CPU) (μs), or Time (user CPU) (μs). And in some cases, I'm seeing the Time (system CPU) come back in ns regardless of what I've chosen.

I suspect it'll be a little easier to track if you can either nail is down explicitly across the board (and sometimes forcing a "round to 0" result), or just letting them float with whatever comes back from the metric gathering system and floating with the relevant range.

hassila added a commit that referenced this issue Mar 2, 2023
…, improve debugging (#76)

## Description

Fixes #66 
Fixes #68 
Fixes #71

Adds regex filtering to debug runs, make CPU time units conform to user
specified time unit also for cpu total/user/cpu times. Add `--scale`
option to command line to get output scaled to per-subiteration values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant