client: Support both sync and async interface for tsoStream, to avoid potential performane regression when concurrent RPC is not enabled

[MyonKeminta]

What problem does this PR solve?

Issue Number:

• Ref client: Support TSO RPC Parallelizing #8432
• Ref PR#56093 may cause 8.8% performance regression in benchmarksql pingcap/tidb#56103

What is changed and how does it work?

client: Support both sync and async interface for tsoStream, to avoid potential performane regression when concurrent RPC is not enabled

The issue pingcap/tidb#56103 reports a performance regression introduced by PR pingcap/tidb#56093 , which introduces #8483 to TiDB.

It's reasonable that this PR does have risk to introduce performance regression in non-current mode (which would be default after finishing #8432). However:

• After I rerun the failed bisect task twice, both of these reruns failed to reproduce the regression.
• According to the previously done microbench (mentioned here), the additional overhead introduced by that PR should not be that much.

So I think the performance regression report looks quite doubtful.

Anyway, I still prepared this PR: the tsoStream provides both sync and async interface. When concurrent RPC is not enabled, the sync interface will be used, making the logic the same as that before merging #8483 .

Check List

Tests

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

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

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

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 bufferflies 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

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

[codecov]

Codecov Report

Attention: Patch coverage is 69.86301% with 22 lines in your changes missing coverage. Please review.

Project coverage is 77.66%. Comparing base (71f6f96) to head (16b59c7).
Report is 18 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8636      +/-   ##
==========================================
+ Coverage   77.57%   77.66%   +0.09%     
==========================================
  Files         474      474              
  Lines       62033    62125      +92     
==========================================
+ Hits        48122    48251     +129     
+ Misses      10355    10313      -42     
- Partials     3556     3561       +5     

Flag	Coverage Δ
unittests	77.66% <69.86%> (+0.09%)	⬆️

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

[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]

@MyonKeminta: 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-integration-realcluster-test	16b59c7	link	false	/test pull-integration-realcluster-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.

[lhy1024]

This means that if we don't turn on the newly introduced feature, it will always work in a synchronized way, do I understand correctly?

[MyonKeminta]

Yes. But let's hold this PR for now as the performance regression is currently very likely to be a misreport due to the unstable test environment.

[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-sigs/prow repository.