Expand sql_planner benchmark for benchmarking physical and logical optimization.#17276
Merged
Conversation
Contributor
Author
|
Here is an instrumented output from running the new logical_plan_optimize benchmark. Compared to the results I see with my actual code the type_coercion in execute_and_check is much faster (I suspect it's because the benchmark isn't using a ListingTable with many files behind it) however the pushdown filter rules takes more time. Adjusting the column count up in the benchmark increases the time significantly. |
alamb
approved these changes
Aug 24, 2025
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
2 participants
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?
Part of #17261
Rationale for this change
Adding/updating benchmarks to allow for making it easier for others to investigate planning performance concerns.
What changes are included in this PR?
sql_planner benchmark update.
Are these changes tested?
Yes.
Are there any user-facing changes?
No