Support binding CPU to isolate query and other threads

[JinheLin]

What problem does this PR solve?

Issue Number: close #1720

This PR is the combination of several PRs(#3089 #3107 #3108 #3126) in hotfix-5.1.1-patch1 branch with some compilation problem fixes.

What is changed and how it works?

Proposal: Support binding CPU to isolate query and other threads

What's Changed:

1. Add singleton CPUAffinityManager to manage CPU affinity of threads by the Linux system call sched_setaffinity .
2. CPUAffinityManager::bindThreadCPUAffinity would bind threads to different CPUs according to the thread's name after all thread-pools are started.
3. MPP tasks don't use thread-pool, they create new threads dynamically, so we should set cpu affinity after new threads are created.
4. The thread-pool of GRPC that MPP tasks used are created dynamically too. Currently, we set cpu affinity in the FlashSerice interface.
5. This function is disabled by default and you can set configuration cpu.query_cpu_percent between 1~100 to enable it.

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

Release note

none

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• flowbehappy

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.

[JinheLin]

/run-all-tests

[flowbehappy]

Looks like this PR fail to compile on MacOS.

In file included from /Users/flow/workspace/github/theflash/storage/ch/dbms/src/Common/CPUAffinityManager.cpp:1:
/Users/flow/workspace/github/theflash/storage/ch/dbms/src/Common/CPUAffinityManager.h:68:21: error: unknown type name 'cpu_set_t'
    void initCPUSet(cpu_set_t & cpu_set, int start, int count);

[flowbehappy]

I think we don't need to put it into release notes and documents. Because

• It is difficult to decide the cpu.query_cpu_percent setting by users.
• We haven't proved that it really works.

So let's make it a hidden feature, only enable it when necessary.

[flowbehappy]

LGTM

[JinheLin]

/merge

[ti-chi-bot]

@JinheLin: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 43ecbb7

[ti-chi-bot]

@JinheLin: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.