Remove tracing from trivial hot functions #435
Merged
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.
When using tracing for profiling purposes, certain uninteresting functions are called over and over, adding overhead specifically when tracing is turned on, rendering the traces useless for profiling purposes. For example, enabling tracing increases the time to create page tables from around 20-40 micro seconds, to over 3 ms (because for example
write_u64
is called many times, generating traces for each call). This PR removes some tracing for hot and trivial functions to avoid unnecessary performance hits.This pr also:
tracing-*
formatPR easiest to review by commits.