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

Investigate using gc.time() in measure() #2

Open
nealrichardson opened this issue Feb 12, 2021 · 0 comments
Open

Investigate using gc.time() in measure() #2

nealrichardson opened this issue Feb 12, 2021 · 0 comments

Comments

@nealrichardson
Copy link
Contributor

Probably instead of the other gc_info. When looking for code regressions, we may want to focus on total_time - gc_time, especially if gc_time is highly variable.
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
1 participant
@nealrichardson