-
Notifications
You must be signed in to change notification settings - Fork 702
sys var: consider global sort for tidb_ddl_reorg_max_write_speed
(#21643)
#21669
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
sys var: consider global sort for tidb_ddl_reorg_max_write_speed
(#21643)
#21669
Conversation
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ti-chi-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request enhances the documentation for the tidb_ddl_reorg_max_write_speed
system variable, providing crucial clarity on its behavior, particularly when TiDB's Global Sort feature is active. The update includes an example to better illustrate how this variable influences write bandwidth during index backfilling in various cluster configurations.
Highlights
- Clarified Scope of System Variable: The documentation for
tidb_ddl_reorg_max_write_speed
now explicitly states that this variable limits the write bandwidth from a single TiDB node to a single TiKV node during index backfilling. - Impact of Global Sort: A new note has been added to explain that when Global Sort is enabled, multiple TiDB nodes can write to TiKV concurrently, which can significantly increase the overall effective write bandwidth.
- Illustrative Example: An example is provided to demonstrate how the
tidb_ddl_reorg_max_write_speed
setting translates to total write bandwidth in a multi-TiDB node cluster, differentiating between scenarios where Global Sort is enabled or disabled.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the documentation for the tidb_ddl_reorg_max_write_speed
system variable to clarify its behavior, especially when Global Sort is enabled. An example is added to illustrate the impact of Global Sort on the total write bandwidth. My review focuses on improving the clarity and precision of the new example text.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is an automated cherry-pick of #21643
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
tidb_ddl_reorg_max_write_speed
docs-cn#20334Do your changes match any of the following descriptions?