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

Measure elapsed time using time.perf_counter() #1758

Merged
merged 2 commits into from
May 7, 2021

Conversation

cyberw
Copy link
Collaborator

@cyberw cyberw commented May 7, 2021

... instead of a mix of time.monotonic(), which sometimes has less precision, and timeit (used in FastHttpUser), which has undesirable effects like disabling GC.

Also, in FastHttpUser, dont round response times to millisecond for no reason.

Note: On Linux/mac .perf_counter() calls .monotonic() in the end, so there is no difference there

cyberw added 2 commits May 7, 2021 12:20
…me.monotonic(), which has less precision (on windows), and timeit (used in FastHttpUser), which has undesirable effects like disabling GC.

Also, in FastHttpUser, dont round response times to millisecond for no reason.
…p a teensy bit more to reduce flakiness of this test.
@cyberw cyberw force-pushed the measure_elapsed_time_with-time.perf_counter() branch from bccd851 to 3b5199d Compare May 7, 2021 10:24
@cyberw
Copy link
Collaborator Author

cyberw commented May 7, 2021

Force push for better commit messages :)

@cyberw cyberw merged commit d9269f1 into master May 7, 2021
@cyberw cyberw deleted the measure_elapsed_time_with-time.perf_counter() branch March 22, 2022 10:18
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

Successfully merging this pull request may close these issues.

1 participant