UCP: Add execution information in slow log Plan field. #15008
Comments
3 tasks
crazycs520
changed the title
|
/pick-up-challenge |
|
@TennyZhuang already had picked #15009, finish it before pick up a new one. |
|
/pick-up-challenge |
|
@TennyZhuang pick up issue success |
|
/give-up-challenge |
|
@Fullstop000 give up issue success |
|
/pick-up-challenge |
|
@TennyZhuang pick up issue success |
|
This pick has been automatically canceled after more than a week. |
|
/pick-up-challenge |
|
@TennyZhuang pick up issue success |
|
This pick has been automatically canceled after more than a week. |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This is the subtask of issue #14974.
Collect execution information like explain analyze
explain analyze(see doc) will collect execution information of each operator, It is very easy to see which operator is slow.Currently, the slow log has recorded the execution
Plan(see PR), we can store the execution information of each operator in thePlantoo, just like theexplain analyze.** Another need todo**
You need to do a benchmark test to see the performance impact.
Score
Mentor(s)
Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace
Recommended Skills
Learning Materials
The text was updated successfully, but these errors were encountered: