-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planner: let CopTiFlashConcurrencyFactor inflence the cost of whole plan (#24157) #24488
Conversation
Signed-off-by: ti-srebot <[email protected]>
/run-all-tests |
@hanfei1991 you're already a collaborator in bot's repo. |
/LGTM |
@fzhedu: In response to this:
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. |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: c259a5c
|
/merge |
/merge |
cherry-pick #24157 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/24488
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Problem Summary:
Sometimes optimizer doesn't choose mpp plan. We lack a way to suggest optimizer choose mpp. I think tiflash_concurrency_factor is a good variable to charge this.
What is changed and how it works?
What's Changed:
The final mpp plan's cost will devide this factor.
How it Works:
Related changes
Check List
Tests
Release note