Change timer to perf_counter #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
change timer to time.perf_counter
remove comment
|
Thanks for the contribution! |
Crypto-Spartan
pushed a commit
to Crypto-Spartan/aioping
that referenced
this pull request
Oct 30, 2020
Change timer to perf_counter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, aioping is set to use time.time or time.clock for it's ping time. I'm proposing a switch to time.perf_counter, as it has a much higher tick rate than time.time or time.clock. time.perf_counter also includes time during sleep, which time.process_time does not.
https://stackoverflow.com/questions/52222002/what-is-the-difference-between-time-perf-counter-and-time-process-time/52228375
https://www.webucator.com/blog/2015/08/python-clocks-explained/