in_memory_engine: adjust the default config#17751
in_memory_engine: adjust the default config#17751ti-chi-bot[bot] merged 12 commits intotikv:masterfrom
Conversation
Signed-off-by: glorv <glorvs@163.com>
| // The maximum interval for GC run is 10 minutes which equals to the minimum | ||
| // value of TiDB GC lifetime. | ||
| const MAX_GC_RUN_INTERVAL: Duration = Duration::from_secs(600); | ||
| // the maximum write kv throughput(20MiB), this is an empiracal value. |
There was a problem hiding this comment.
| // the maximum write kv throughput(20MiB), this is an empiracal value. | |
| // the maximum write kv throughput(20MiB), this is an empirical value. |
| const MAX_GC_RUN_INTERVAL: Duration = Duration::from_secs(600); | ||
| // the maximum write kv throughput(20MiB), this is an empiracal value. | ||
| const MAX_WRITE_KV_SPEED: u64 = 20 * 1024 * 1024; | ||
| // The maximun duration in seconds we expect IME to release enough memory after |
There was a problem hiding this comment.
| // The maximun duration in seconds we expect IME to release enough memory after | |
| // The maximum duration in seconds we expect IME to release enough memory after |
| // We use this value to determine the default value of `evict_threshold` based | ||
| // on `capacity`. | ||
| const MAX_RESERVED_DURATION_FOR_WRITE: u64 = 10; | ||
| // Regions' mvcc read amplificatoin statistics is updated every 1min, so we set |
There was a problem hiding this comment.
| // Regions' mvcc read amplificatoin statistics is updated every 1min, so we set | |
| // Regions' mvcc read amplification statistics is updated every 1min, so we set |
|
/retest |
| // the maximum write kv throughput(20MiB), this is an empirical value. | ||
| const MAX_WRITE_KV_SPEED: u64 = 20 * 1024 * 1024; | ||
| // The maximum duration in seconds we expect IME to release enough memory after | ||
| // memory usage reaches `evict_threshold`. This is an empiracal value. |
There was a problem hiding this comment.
| // memory usage reaches `evict_threshold`. This is an empiracal value. | |
| // memory usage reaches `evict_threshold`. This is an empirical value. |
[LGTM Timeline notifier]Timeline:
|
Signed-off-by: glorv <glorvs@163.com>
Signed-off-by: glorv <glorvs@163.com>
|
/retest |
|
/retest |
|
@zhangjinpeng87 PTAL |
|
@glorv: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: overvenus, SpadeA-Tang, zhangjinpeng87 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 |
ref tikv#16141, close tikv#17762 Let in_memory_engine's config`evict-threshold` and `stop-load-threshold` default value generated from `capacity`. Signed-off-by: glorv <glorvs@163.com>
What is changed and how it works?
Issue Number: ref #16141, close #17762
What's Changed:
evict-threshold: default value set to capacity - min(capacity * 0.1, 200MiB)stop-load-threshold: default value set to: evict_threshold - min(capacity * 0.15, region_split_size * 2 + 200MiB)load-evict-intervalto 120s as the background task will skip the check if the interval is small than 90s.LoadEvictObserverfrom info to debug as RegionManager will also output these logs.ratetodeltaas the rate is too small and we care the actual event number than its rate.Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note