perf: Optimize DFSchema::qualified_name#21722
Open
neilconway wants to merge 3 commits intoapache:mainfrom
Open
perf: Optimize DFSchema::qualified_name#21722neilconway wants to merge 3 commits intoapache:mainfrom
DFSchema::qualified_name#21722neilconway wants to merge 3 commits intoapache:mainfrom
Conversation
950ff50 to
a426316
Compare
Contributor
Author
|
run benchmark sql_planner |
|
🤖 Criterion benchmark running (GKE) | trigger CPU Details (lscpu)Comparing neilc/perf-planner-qualified-name (ec144c1) to b75df6f (merge-base) diff File an issue against this benchmark runner |
|
🤖 Criterion benchmark completed (GKE) | trigger Instance: CPU Details (lscpu)Details
Resource Usagebase (merge-base)
branch
File an issue against this benchmark runner |
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 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.
Which issue does this PR close?
DFSchema::qualified_name#21723Rationale for this change
DFSchema::qualified_nameshows up as a hotspot when profiling the planner. It currently goes through thefmtmachinery, which is fairly slow; it is reasonably simple to avoid that andwrite_str()to a preallocated string.On the
sql_plannerbenchmark, this yields 1-5% improvements for most benchmarks, with no significant regressions.What changes are included in this PR?
qualified_nameandTableReference::DisplayAre these changes tested?
Yes.
Are there any user-facing changes?
No.