grpc-io: upgrade to latest version - v0.13.0.

[LykxSassinator]

What is changed and how it works?

Issue Number: Close #xxx

What's Changed:

Upgrade the grpc-io lib to the latest version - v0.13.0.

Meanwhile, the format of `cargo.toml` is re-arranged and become tidier than the older version.

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• Need to cherry-pick to the release branch

Check List

Tests

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

Side effects

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

Release note

Upgrade the grpc-io lib to the latest version - v0.13.0.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• bufferflies

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.

[bufferflies]

You need to compare the performance between the current and this pr.

[LykxSassinator]

You need to compare the performance between the current and this pr.

Thx for reminding.
Yep, I will add and supply the performance testing results between master and this pr.

[LykxSassinator]

/test

[LykxSassinator]

/test retry=7

[LykxSassinator]

/test threads=4 retry=7

[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.}

[LykxSassinator]

Maybe this pr could be paused, found two problems to this pr:

• According to testing records, based on TPCC workloads, the newly upgraded version v0.13.0 caused the raising on CPU.usage, about ~12% to ~15% based on the results.
• The uts still have some abnormal cases which cannot be fixed directly, throwing SIGABRT signal and aborting all consequential cases. Basically, I've tried to replace the unsafe tokio::runtime with the safe RuntimeWrapper, which will safely releasing the Runtime object when drop. But some uts still are hung by the abnormal signal SIGABRT.

Related issue to grpc-io can be reviewed in: tikv/grpc-rs#643

PS: By testing with tpcc-1000 warehouses (CPU: 16 cores) , the performance results can be reviewed in the following table. And the throughput didn't differ a lot, but the CPU.usage on upgrading v0.13.0 is much higher than the nightly version.

• QPS part: (higher is better)

Concurrency	upgrading v0.13.0	Master (nightly version)
50 threads	20841	21272
100 threads	21552	21640
150 threads	21378	21531
200 threads	20586	21104

• CPU part: (higher means more cost on CPU.usage)

Concurrency	upgrading v0.13.0	Master (nightly version)
50 threads	1421%	1283%
100 threads	1530%	1347%
150 threads	1610%	1422%
200 threads	1645%	1464%

[ti-chi-bot]

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.

[ti-chi-bot]

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

Test name	Commit	Details	Required	Rerun command
pull-unit-test	84721d2	link	true	/test pull-unit-test

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