cop: display kv read time details in the execution information

[cfzjywxk]

What problem does this PR solve?

Issue Number: ref #28937

Problem Summary:

explain analyze select * from t1;
+-----------------------+---------+---------+-----------+---------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+-----------+------+
| id                    | estRows | actRows | task      | access object | execution info                                                                                                                                                                                                                                                                                                                                               | operator info                               | memory    | disk |
+-----------------------+---------+---------+-----------+---------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+-----------+------+
| TableReader_5         | 6.00    | 6       | root      |               | time:104.4ms, loops:2, RU:0.714463, cop_task: {num: 1, max: 104.2ms, proc_keys: 6, tot_proc: 704.9µs, tot_wait: 513.1µs, rpc_num: 1, rpc_time: 104.1ms, copr_cache_hit_ratio: 0.00, build_task_duration: 553.6µs, max_distsql_concurrency: 1}                                                                                                                | data:TableFullScan_4                        | 542 Bytes | N/A  |
| └─TableFullScan_4     | 6.00    | 6       | cop[tikv] | table:t1      | tikv_task:{time:104ms, loops:1}, scan_detail: {total_process_keys: 6, total_process_keys_size: 295, total_keys: 7, get_snapshot_time: 206.9µs, rocksdb: {key_skipped_count: 6, block: {cache_hit_count: 2}}}, total_process_time: 704.9µs, total_suspend_time: 100.9ms, total_wait_time: 513.1µs, total_kv_read_wall_time: 104ms, tikv_wall_time: 103.1ms    | keep order:false, stats:partial[k1:missing] | N/A       | N/A  |
+-----------------------+---------+---------+-----------+---------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+-----------+------+

The `total_kv_read_wall_time` could be displayed in the execution information.

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

Documentation

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @cfzjywxk. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cfzjywxk]

Em... The cache is not updated. sigh...

[zyguan]

/retest

[tiprow]

@zyguan: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[zyguan]

/ok-to-test

[codecov]

Codecov Report

Merging #52146 (c6cf92f) into master (923b071) will increase coverage by 2.0460%.
Report is 2 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52146        +/-   ##
================================================
+ Coverage   72.1432%   74.1892%   +2.0460%     
================================================
  Files          1467       1467                
  Lines        426679     426733        +54     
================================================
+ Hits         307820     316590      +8770     
+ Misses        99681      90299      -9382     
- Partials      19178      19844       +666     

Flag	Coverage Δ
integration	48.2269% <100.0000%> (?)
unit	70.9565% <100.0000%> (-0.0723%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	49.3520% <ø> (+8.7442%)	⬆️

[cfzjywxk]

/test check-dev2

[tiprow]

@cfzjywxk: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ekexium]

Can we have a unit test for it?

[cfzjywxk]

Can we have a unit test for it?

@ekexium The test is added, PTAL

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-28 01:55:36.304690467 +0000 UTC m=+2119363.326936855: ☑️ agreed by zyguan.
• 2024-03-28 08:34:19.822743362 +0000 UTC m=+2143286.844989750: ☑️ agreed by ekexium.

[windtalker]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ekexium, windtalker, zyguan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ekexium,windtalker,zyguan]
• pkg/distsql/OWNERS [windtalker]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cfzjywxk]

/retest

[cfzjywxk]

/retest

[cfzjywxk]

/test check-dev2

[tiprow]

@cfzjywxk: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cfzjywxk]

/test check-dev2

[tiprow]

@cfzjywxk: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cfzjywxk]

/retest

[cfzjywxk]

/test check-dev2

[tiprow]

@cfzjywxk: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.