Skip to content
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

NUMA 架构下,是否还应限制单服务使用的内存 #10508

Open
Icemap opened this issue Jul 13, 2022 · 2 comments
Open

NUMA 架构下,是否还应限制单服务使用的内存 #10508

Icemap opened this issue Jul 13, 2022 · 2 comments
Assignees
Labels
area/deploy-upgrade-maintain Indicates that the Issue or PR belongs to the area of deployment, upgrade, and maintenance.

Comments

@Icemap
Copy link
Member

Icemap commented Jul 13, 2022

Error 报告

This repository is ONLY used to solve problems related to DOCS-CN.
For other issues (TiDB, TiKV, etc), please move to other repositories.

Please answer the following questions before submitting your issue. Thanks!

  1. What is the document directory for the problem?
  1. How would you like to improve it?

原文:
image

此处提到了 NUMA 架构,但未限制单进程的内存用量,这有可能会导致跨 NUMA Node 访问内存。跨 NUMA Node 访问内存,会极大地降低性能(早期服务器 7 倍,后期 1.3 倍)。
仅限制了:

  • 进程数 = NUMA CPU 的个数 (其实此处是否应该使用 NUMA Node 数物理 CPU 数 替代 NUMA CPU 的个数 来消除歧义?)
  • 单个 NUMA Node 中 CPU 的核心数 = max-procs

那么在使用过程中,肯定会有部分 TiDB 申请额外的 NUMA Node 外的内存,因为进程并非绝对平分内存。应额外添加:

  • 单个 TiDB 进程可使用的内存上限 = 单个 NUMA Node 内的内存容量 (即:单路内存容量)

限制进程内存使用。

@shichun-0415 shichun-0415 added area/deploy-upgrade-maintain Indicates that the Issue or PR belongs to the area of deployment, upgrade, and maintenance. labels Jul 14, 2022
@shichun-0415 shichun-0415 self-assigned this Jul 14, 2022
@shichun-0415
Copy link
Contributor

@Icemap 谢谢反馈。@qqqdan 请帮忙确认下可以吗?

@qqqdan
Copy link
Contributor

qqqdan commented Jul 14, 2022

性能测试的相关内容我不太熟悉,请问 @dbsid 焕生老师这边有没有建议?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/deploy-upgrade-maintain Indicates that the Issue or PR belongs to the area of deployment, upgrade, and maintenance.
Projects
None yet
Development

No branches or pull requests

3 participants