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.

Sign up for GitHub

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

Jump to bottom

CPU time option #69

Open
gsnedders opened this issue May 9, 2020 · 2 comments
Open

CPU time option #69

gsnedders opened this issue May 9, 2020 · 2 comments

Comments

@gsnedders
Copy link

For some uses, it would be nice to measure CPU time rather than wall-clock time.
@vstinner
Copy link
Member

Hi. Which API do you want to specify which clock should be used? A parameter to Runner()? A parameter to bench*() functions? Both?

@gsnedders
Copy link
Author

At an API level I think parameter to Runner? Having a single Runner having some wall-clock timed and some CPU timed seems like it would probably be confusing in terms of understanding what is being measured.

That said, I was mostly thinking about the CLI and imagining another option like --tracemalloc/--track-memory changing what is measured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gsnedders @vstinner