sst_importer: Get Memory limit at the sst service initialization#18321
sst_importer: Get Memory limit at the sst service initialization#18321ti-chi-bot[bot] merged 4 commits intotikv:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
Signed-off-by: 3pointer <luancheng@pingcap.com>
81828e6 to
24a20ce
Compare
|
/ok-to-test |
Signed-off-by: 3pointer <luancheng@pingcap.com>
Signed-off-by: 3pointer <luancheng@pingcap.com>
Signed-off-by: 3pointer <luancheng@pingcap.com>
ea32350 to
b1374c2
Compare
|
lgtm, thanks for the change! (I don't have permission to approve yet.) I think for a quick bandaid it works but for the long term I feel like we could add a mem limit cache to our sys crate, and do background refresh every second or so, or just let next api call to update the cache. so not every call can trigger a sys call. That way we can get mem refresh not so often |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Leavrth, YuJuncen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
close tikv#18317, close pingcap/tidb#60140 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What is changed and how it works?
Issue Number: Close #18317
and close pingcap/tidb#60140
What's Changed:
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note