-
Couldn't load subscription status.
- Fork 705
tidb: update tidb_index_serial_scan_concurrency docs #21938
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
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Pull Request Overview
This PR updates documentation to reflect the deprecation of the tidb_index_serial_scan_concurrency variable. The variable is no longer modifiable, and its functionality has been replaced by tidb_executor_concurrency for sequential index scans and tidb_analyze_distsql_scan_concurrency for ANALYZE operations.
Key Changes:
- Deprecates
tidb_index_serial_scan_concurrencywith a warning that directs users to the replacement variables - Removes references to the deprecated variable from troubleshooting and performance benchmarking guides
- Updates configuration examples to use
tidb_analyze_distsql_scan_concurrencyinstead of the deprecated variables
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| system-variables.md | Adds deprecation warning and updates description to indicate the variable is kept for backward compatibility only |
| statistics.md | Consolidates documentation by removing the separate section for tidb_index_serial_scan_concurrency and updating tidb_analyze_distsql_scan_concurrency to note its expanded role |
| troubleshoot-tidb-oom.md | Removes deprecated variable from the list of concurrency controls for reducing memory usage |
| tidb-cloud/v8.5-performance-benchmarking-with-tpcc.md | Replaces deprecated variables with tidb_analyze_distsql_scan_concurrency in TPC-C test setup |
| tidb-cloud/v8.1-performance-benchmarking-with-tpcc.md | Replaces deprecated variables with tidb_analyze_distsql_scan_concurrency in TPC-C test setup |
| best-practices/tidb-best-practices.md | Updates reference from deprecated variable to tidb_executor_concurrency for controlling index scan behavior |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
fix: v8.1 fix: v8.5 fix: tidb_analyze_distsql_scan_concurrency fix: tidb_index_serial_scan_concurrency fix: fix: 8.1 fix: 8.5 fix: update links fix: update fix fix: typo fix: update fix: default value fix: update fix: update fix: update fix: update
f87d569 to
bb45b6d
Compare
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.
🔢 Self-check (PR reviewed by myself and ready for feedback)
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.
Pull Request Overview
Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
/cc @terry1purcell |
|
@0xPoe: GitHub didn't allow me to request PR reviews from the following users: terry1purcell. Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs. 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 kubernetes-sigs/prow repository. |
| - This variable is used to set the sampling concurrency in the `ANALYZE` process. | ||
| - When the variable is set to a larger value, the execution performance of other queries is affected. | ||
| - Used to control the concurrency level for merging samples collected from different regions. | ||
| - Used to control the concurrency for special indexes (such as indexes on generated virtual columns), for example, how many indexes can collect statistics simultaneously. |
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.
This "check warning" is complaining about the word "many" in "how many indexes". You may want to use "for example, the number of indexes which can concurrently collect statistics".
| - Unit: Threads | ||
| - This variable is used to set the concurrency of executing the `ANALYZE` statement. | ||
| - When the variable is set to a larger value, the execution performance of other queries is affected. | ||
| - For manual analyze: used to control the concurrency of table or partition analysis — for example, how many partition or table tasks can be processed simultaneously. |
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.
You may want to use "the number of partitions or table tasks that can be processed simultaneously".
| - Default value: `1` | ||
| - Range: `[1, 256]` | ||
| - This variable is used to set the concurrency of executing the automatic update of statistics. | ||
| - For auto analyze: used to control the concurrency of table or partition analysis — for example, how many partition or table tasks can be processed simultaneously. |
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.
You may want to use "the number of partitions or table tasks that can be processed simultaneously".
| #### `tidb_build_stats_concurrency` | ||
|
|
||
| When you run the `ANALYZE` statement, the task is divided into multiple small tasks. Each task only works on statistics of one column or index. You can use the [`tidb_build_stats_concurrency`](/system-variables.md#tidb_build_stats_concurrency) variable to control the number of simultaneous small tasks. The default value is `2`. The default value is `4` for v7.4.0 and earlier versions. | ||
| Used to control the concurrency of table or partition analysis — for example, how many partition or table tasks can be processed simultaneously. The default value is `2`. The default value is `4` for v7.4.0 and earlier versions. |
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.
You may want to use "the number of partitions or table tasks that can be processed simultaneously".
|
|
||
| When analyzing ordinary columns, you can use [`tidb_build_sampling_stats_concurrency`](/system-variables.md#tidb_build_sampling_stats_concurrency-new-in-v750) to control the concurrency of executing sampling tasks. The default value is `2`. | ||
| 1. Used to control the concurrency level for merging samples collected from different regions. | ||
| 2. Used to control the concurrency for special indexes (such as indexes on generated virtual columns), for example, how many special indexes can collect statistics simultaneously. |
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.
You may want to use "the number of special indexes that can collect statistics simultaneously".
First-time contributors' checklist
What is changed, added or deleted? (Required)
See: pingcap/tidb#64023
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?