PGDO: lookup only self time #204
Merged
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
Long runs can take a long time to do instruction-pointer lookup. However, since we only credit the "self" time there is no need to look up everything. This limits the lookup to the triggering instruction pointer. It also attributes the cost to the whole "inlining chain."
d6098f4 to
99835e7
Compare
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.
Long runs can take a long time to do instruction-pointer lookup.
However, since we only credit the "self" time there is no need to
look up everything. This limits the lookup to the triggering instruction
pointer. It also attributes the cost to the whole "inlining chain."