Try to calculate inherit cost of nanoTime() #503
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
Benchmark nanoTime() cost by running multiple iterations to get the avg time spent inside nanoTime() This helps improve reliability of FrameTimer, since calling begin() & end() for the same timer multiple times can lead to a phantom time as the cost of calling nanoTime() is instead timed
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.
Problem:
Invoking Begin & End on a timer multiple times, IE: tileInFrustum() can lead to nanoTime() invocation time bleeding into timer
Proposed Solution:
Benchmark nanoTime() cost by running multiple iterations to get the avg time spent inside nanoTime() This helps improve reliability of FrameTimer.