# Summary

+ Analysis conclusion:
  + The TiDB Duration time and the KV Request time and the TiKV gRPC message duration basically correspond, and you can basically confirm that the slowness is on the TiKV side
  + Comparing KV Request Duration 99 by Store and 99% gRPC message duration, it can be seen that the time consumed by TiKV is not related to the network, and the focus is on troubleshooting TiKV internal.
+ Further confirm the direction:
  + TiKV internal processing process

------------------------------------------------------------
From the above monitoring, you can see the basic correspondence between the TiDB Duration time and the KV Request time and the TiKV gRPC message duration. Basically, you can confirm the slowness on the TiKV side. Subsequent troubleshooting can be focused on the TiKV Details monitoring.
Potential network problems can be found by comparing the gRPC duration of TiKV and the KV duration in TiDB. At present, the time can basically be matched to rule out network problems. Check out the Scheduler Duration further.