feat(planner): Support EXPLAIN ANALYZE statement to profile query execution
#10023
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
mergify
bot
added
the
pr-feature
BohuTANG
reviewed
Feb 14, 2023
BohuTANG
reviewed
Feb 14, 2023
src/query/service/src/pipelines/processors/transforms/transform_cast_schema.rs
Show resolved
Hide resolved
BohuTANG
reviewed
Feb 14, 2023
zhang2014
approved these changes
Feb 14, 2023
|
Add doc: #10027 |
3 tasks
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.
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
A naive implementation of
EXPLAIN ANALYZEstatement.In this PR, we introduced a framework to help us profile queries.
The processing time of processors is collected and accumulated and will be displayed along with the corresponding SQL operator.
For example:
This metric is helpful in figuring out which SQL operator is critical in most scenarios.
More metrics will be added later.
Closes #9927