server:return qps data to tidbdashborad

[qidi1]

Signed-off-by: qidi1 1083369179@qq.com

What problem does this PR solve?

Currently，Keyviz has keys and bytes dimensions. In some situations, it cannot find the hotspot that the CPU is high caused by QPS, the keys and bytes may be 0. For example:

create table t(id int);
insert into table t values (1)(2)....(1000);
// random read out bound，suppose there are many requests.
select * from t where id = 1000 + rand(0,1000)

Issue Number: #pingcap/tidb-dashboard/issues/1209

What is changed and how does it work?

Return QPS data in PD.

Check List

Tests

• Unit test
• Manual test

Related changes

• server:add querystats sync to follower pd  #4922
• proto:add querystat in SyncRegionResponse  pingcap/kvproto#914
• add QPS in tidb_dashboard ref:#1209 pingcap/tidb-dashboard#1252

Release note

None

Manual test

We ran a small cluster locally. On the cluster, test data was generated using the tiup bench tool. The results are shown in the figure below.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456, multiple issues should use full syntax for each issue and be separated by a comma, like: Issue Number: close #123, ref #456.

_{📖 For more info, you can check the "Linking issues" section in the CONTRIBUTING.md.}

[ti-chi-bot]

@qidi1: PR needs rebase.

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.