Prefer erlang:monotonic_time/0 for elapsed time measurements (backport #10928)
#10994
Conversation
This file contains hidden or 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
This is now the recommended way to measure durations with the time API: <https://www.erlang.org/doc/apps/erts/time_correction#how-to-work-with-the-new-api> (cherry picked from commit 1b35c3f)
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.
This is now the recommended way to measure durations with the time API: https://www.erlang.org/doc/apps/erts/time_correction#how-to-work-with-the-new-api. This is mostly a cosmetic change though since it's only used in/for log messages.
\cc @dumbbell I've changed the log message for the time it takes to regen the feature flag registry to be milliseconds instead of microsecond as it takes ~35-40ms for me locally. (Similar to #10674)
This is an automatic backport of pull request #10928 done by Mergify.