BatchPointGet execution info enhancement
Open
report/customer
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
For a slow batchPointGet executor:
Lacks more detailed info to explain why the executor takes so much time:
1. 8 rpc, total_time is 316ms, it lacks the slowest rpc time and its target tikv addr
2. Needs more fine grained time stats for rpc time, like grpc_queue time
3. For non-clustered index, batchPointGet needs twice rpc, one for handle, one for data, we'd better distinguish these two types rpc.
Contributor guide
Assessment
This issue has not been assessed yet.