bench: add logging benchmarks for LogPrintLevel and LogPrintfCategory#25586
Closed
jonatack wants to merge 4 commits intobitcoin:masterfrom
Closed
bench: add logging benchmarks for LogPrintLevel and LogPrintfCategory#25586jonatack wants to merge 4 commits intobitcoin:masterfrom
jonatack wants to merge 4 commits intobitcoin:masterfrom
Conversation
478272d to
f896ef9
Compare
f896ef9 to
147f479
Compare
Member
|
~0 - I'm not really convinced we need more benchmarks for logging code. |
Member
Author
|
This change makes sense given that the codebase is migrating to these methods but closing for now, will try again later. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
LogPrintLevel and LogPrintfCategory were recently added to the logging macros in #24464 and #25306, respectively. Our logging is expected to primarily use these methods, so it makes sense to benchmark them.
This pull adds benchmarks for both of them to the logging benchmarks, improves the existing benchmark naming to be clearer and with a more coherent output order, and sorts the benchmark code in that order.
after