Skip to content

docs: fix tidb_server_memory_limit unit description #23588

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.

Sign up for GitHub

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

Open
doc-claw-bot wants to merge 3 commits into
base: release-7.5
Choose a base branch
from
Open

docs: fix tidb_server_memory_limit unit description #23588

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2ba5a87
docs: fix tidb_server_memory_limit unit description
doc-claw-bot Aug 21, 2026
24abbae
Apply suggestion from @qiancai
qiancai Aug 21, 2026
7e14197
docs: fix session memory limit unit description
qiancai Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions system-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4823,7 +4823,7 @@ SHOW WARNINGS;
- Default value: `80%`
- Range:
- You can set the value in the percentage format, which means the percentage of the memory usage relative to the total memory. The value range is `[1%, 99%]`.
- You can also set the value in memory size. The value range is `0` and `[536870912, 9223372036854775807]` in bytes. The memory format with the units "KiB|MiB|GiB|TiB" is supported. `0` means no memory limit.
- You can also set the value in memory size. The value range is `0` and `[536870912, 9223372036854775807]` in bytes. The memory format with units "KB|MB|GB|TB" is supported. For example, you can set this variable to `90GB` (no space between the number and the unit). `0` means no memory limit.
- If this variable is set to a memory size that is less than 512 MiB but not `0`, TiDB uses 512 MiB as the actual size.
- This variable specifies the memory limit for a TiDB instance. When the memory usage of TiDB reaches the limit, TiDB cancels the currently running SQL statement with the highest memory usage. After the SQL statement is successfully canceled, TiDB tries to call Golang GC to immediately reclaim memory to relieve memory stress as soon as possible.
- Only the SQL statements with more memory usage than the [`tidb_server_memory_limit_sess_min_size`](/system-variables.md#tidb_server_memory_limit_sess_min_size-new-in-v640) limit are selected as the SQL statements to be canceled first.
Expand Down Expand Up @@ -4852,7 +4852,7 @@ SHOW WARNINGS;
- Persists to cluster: Yes
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No
- Default value: `134217728` (which is 128 MiB)
- Range: `[128, 9223372036854775807]`, in bytes. The memory format with the units "KiB|MiB|GiB|TiB" is also supported.
- Range: `[128, 9223372036854775807]`, in bytes. The memory format with units "KB|MB|GB|TB" is supported. For example, you can set this variable to `90GB` (no space between the number and the unit).
- After you enable the memory limit, TiDB will terminate the SQL statement with the highest memory usage on the current instance. This variable specifies the minimum memory usage of the SQL statement to be terminated. If the memory usage of a TiDB instance that exceeds the limit is caused by too many sessions with low memory usage, you can properly lower the value of this variable to allow more sessions to be canceled.

### tidb_service_scope <span class="version-mark">New in v7.4.0</span>
Expand Down
Loading