pingcap / pingcap/tidb

Tracking issue for the `tidb_mem_quota_analyze`

Open
#52,544 0 comments 0 reactions 0 assignees View on GitHub
component/statistics sig/planner type/enhancement
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Enhancement
In the past, we introduced `tidb_mem_quota_analyze` to help us control the memory usage of the `analyze` statement.

But the problem is that the default value of this variable is -1, it means we always use the global memory controller to control the memory usage of all queries.

In most cases, we don't enable this feature as the global memory controller is sufficient. We introduced this feature before we added `tidb_mem_server_limit` as a global variable. Currently, they both perform almost the same function so we have decided to deprecate it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.