From 9fa6adcb3e8eb227cb97a1ab03e6bd643e245a5d Mon Sep 17 00:00:00 2001 From: Yasuo Honda Date: Wed, 16 Sep 2026 11:42:08 +0900 Subject: [PATCH] docs: fix inconsistent total in dashboard-metrics-relation.md example The stated total (14745.07 seconds) for TiDB sending key-value requests didn't match the sum of its own two stated components (Get: 9798.02s + Cop: 4946.46s = 14744.48s), a difference too large to be rounding error. Corrected the total to match the sum of its parts. Found via a CodeRabbit review comment on pingcap/docs#23883 (the JA translation faithfully mirrored this EN inconsistency). Co-Authored-By: Claude Sonnet 5 --- dashboard/dashboard-metrics-relation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dashboard/dashboard-metrics-relation.md b/dashboard/dashboard-metrics-relation.md index 25425bee92927..c11d622de065e 100644 --- a/dashboard/dashboard-metrics-relation.md +++ b/dashboard/dashboard-metrics-relation.md @@ -86,4 +86,4 @@ However, it is hard to determine how much duration of `tidb_kv_request` is inclu `tidb_kv_request` does not include `tidb_kv_request.Get` and `tidb_kv_request.Cop` nodes as its child nodes, but consists of the latter two nodes. The name prefix of the child node is the name of the parent node plus `.xxx`, which means that the child node is the sub-class of the parent node. You can understand this case in the following way: -The total duration of TiDB sending key-value requests is 14745.07 seconds, during which the key-value requests for the `Get` and `Cop` types respectively consume 9798.02 seconds and 4946.46 seconds. +The total duration of TiDB sending key-value requests is 14744.48 seconds, during which the key-value requests for the `Get` and `Cop` types respectively consume 9798.02 seconds and 4946.46 seconds.