Split running execution plan into detail stages
Open
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
We recorded the `Query_time`, `Parse_time`, `Compile_time` and some other useful information in `SlowLog`. The users offten find that The `Query_time` is very long but the other stage is very short, in other words, it can't locate where is the time spent.
We should add a `Execution_time` which stands for the time spent in running the exection plan which is generated by the internal `Compile` function whose time is recorded as 'Compile_time'. After this, It's impossible to find the scene that the `Query_time` is very long but the other stage is very short.
Contributor guide
Assessment
This issue has not been assessed yet.