*: Optimize collecting executor runtime stats performance

[crazycs520]

What problem does this PR solve?

Issue Number: ref #56649

Problem Summary: Optimize collecting executor runtime stats performance.

Related PR: tikv/client-go#1532

What changed and how does it work?

• Remove some useless field in struct.
• Avoid memory allocate in heap.
• Adjust the API to reduce consumption.

Before

This PR

Benchmark

version	workload	thread	QPS	QPS Increase
master	oltp_point_select	100	86019
This PR	oltp_point_select	100	87232	1.4%
master	oltp_index_scan(range-size=2)	100	46397
This PR	oltp_index_scan(range-size=2)	100	47679	2.7%
master	oltp_index_lookup(range-size=2)	100	18765
This PR	oltp_index_lookup(range-size=2)	100	19188	2.2%

Check List

Tests

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

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

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

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign windtalker for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS
• pkg/distsql/OWNERS

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

[tiprow]

Hi @crazycs520. 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-sigs/prow repository.

[ti-chi-bot]

@crazycs520: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	c67d8c1	link	true	/test build
idc-jenkins-ci-tidb/unit-test	c67d8c1	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev	c67d8c1	link	true	/test check-dev
idc-jenkins-ci-tidb/check_dev_2	c67d8c1	link	true	/test check-dev2

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.