Add information of hashAgg for memory control#6819
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
/cc @XuHuaiyu |
|
/rebase |
9d4af40 to
72f10e1
Compare
Liuxiaozhen12
left a comment
There was a problem hiding this comment.
not sure the form of command I suggested is correct or not. Just suggestions.
| - 落盘行为会由参数 [`mem-quota-query`](/tidb-configuration-file.md#mem-quota-query),[`oom-use-tmp-storage`](/tidb-configuration-file.md#oom-use-tmp-storage),[`oom-use-tmp-storage`](/tidb-configuration-file.md#oom-use-tmp-storage), [`tmp-storage-path`](/tidb-configuration-file.md#tmp-storage-path),[`tmp-storage-quota`](/tidb-configuration-file.md#tmp-storage-quota) 共同控制。 | ||
| - 当落盘被触发时,会在日志中打印一条包含关键字 `memory exceeds quota, spill to disk now` 或 `memory exceeds quota, set aggregate mode to spill-mode` 的日志。 | ||
| - Sort,MergeJoin,HashJoin 落盘是从 v4.0.0 版本开始引入的,HashAgg 落盘是从 v5.2.0 版本开始引入的。 | ||
| - 含 HashAgg 的 SQL 引起 OOM 时,可以尝试设置 concurrency = 1 来触发落盘。 |
There was a problem hiding this comment.
对于除 HashAgg 外的其他算子,是不是不支持手动设置参数触发落盘呢?
There was a problem hiding this comment.
其他算子落盘是默认开启。 可以通过 oom-use-tmp-storage 来控制所有的落盘行为。
|
|
||
| ## tidb-server 其它内存控制策略 | ||
|
|
||
| ### 流控 |
There was a problem hiding this comment.
写成”流量控制“ 可以吗? ”动态内存控制功能“太宽泛,数据落盘也能算动态内存控制功能
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
|
@XuHuaiyu: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
/remove-status LGT1 |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: d557021 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?