tracing: fix perf regression when release_max_level_* not set #3373
+30
−15
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
|
CI failure started from #3368(https://github.com/tokio-rs/tracing/actions/runs/17332053028/job/49210169731)? |
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.
Motivation
This PR fixes perf regression (binary size and instruction counts) existed in tracing > 0.1.37 in case if
release_max_level_*feature was not set, butmax_level_*was.Solution
Regression was introduced in #2553, where logic was unintentionally changed: before pr, in case if
release_max_level_*wasn't set, log level frommax_level_*was used, but after it was unconditionally set to trace level.See additional info in #2553 (comment)