Should memory usage of tidb-server be limited, and how to limit it in version 6.1.0?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb-server内存要不要限制,6.1.0怎么限制?

| username: xiaoxiaozuofang

【TiDB Usage Environment】Production Environment
【TiDB Version】
【Reproduction Path】What operations were performed that caused the issue
【Encountered Issue: Issue Phenomenon and Impact】Should the memory of tidb-server be limited, and how to limit it in version 6.1.0?
【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】

| username: WalterWj | Original post link

This TiDB 内存控制文档 | PingCAP 文档中心?

| username: tidb菜鸟一只 | Original post link

| username: xiaoxiaozuofang | Original post link

Since PD and TiDB are deployed together, I’m not sure if PD and TiDB are using too much memory. Should the memory usage of the tidb-server instance be limited? How to limit it in the production environment with version 6.1.0?

| username: forever | Original post link

The tidb-server will occupy a relatively large amount of memory. It is best to limit the tidb-server. You can observe the experimental feature in version 6.1.

| username: zhanggame1 | Original post link

Restrictions are still necessary. TiDB can easily run out of memory (OOM). The default 1GB limit for a single SQL execution can be increased a bit.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.