Skip to content

Commit

Permalink
This is an automated cherry-pick of pingcap#15168
Browse files Browse the repository at this point in the history
Signed-off-by: ti-chi-bot <[email protected]>
  • Loading branch information
yahonda authored and ti-chi-bot committed Dec 20, 2023
1 parent f3adeb3 commit e6d8f02
Showing 1 changed file with 25 additions and 0 deletions.
25 changes: 25 additions & 0 deletions system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -2047,6 +2047,31 @@ For a system upgraded to v5.0 from an earlier version, if you have not modified
- Range: `[100, 16384]`
- This variable is used to set the maximum number of schema versions (the table IDs modified for corresponding versions) allowed to be cached. The value range is 100 ~ 16384.
<<<<<<< HEAD
=======
### tidb_max_paging_size <span class="version-mark">New in v6.3.0</span>
- Scope: SESSION | GLOBAL
- Persists to cluster: Yes
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): Yes
- Type: Integer
- Default value: `50000`
- Range: `[1, 9223372036854775807]`
- Unit: Rows
- This variable is used to set the maximum number of rows during the coprocessor paging request process. Setting it to too small a value increases the RPC count between TiDB and TiKV, while setting it to too large a value results in excessive memory usage in some cases, such as loading data and full table scan. The default value of this variable brings better performance in OLTP scenarios than in OLAP scenarios. If the application only uses TiKV as the storage engine, consider increasing the value of this variable when executing OLAP workload queries, which might bring you better performance.
### tidb_max_tiflash_threads <span class="version-mark">New in v6.1.0</span>
- Scope: SESSION | GLOBAL
- Persists to cluster: Yes
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No
- Type: Integer
- Default value: `-1`
- Range: `[-1, 256]`
- Unit: Threads
- This variable is used to set the maximum concurrency for TiFlash to execute a request. The default value is `-1`, indicating that this system variable is invalid and the maximum concurrency depends on the setting of the TiFlash configuration `profiles.default.max_threads`. When the value is `0`, the maximum number of threads is automatically configured by TiFlash.
>>>>>>> ba55227390 (Explain `tidb_max_tiflash_threads` default value `-1` means (#15168))
### tidb_mem_oom_action <span class="version-mark">New in v6.1.0</span>
- Scope: GLOBAL
Expand Down

0 comments on commit e6d8f02

Please sign in to comment.