-
Notifications
You must be signed in to change notification settings - Fork 762
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
chore: bring back function set_cache_capacity
#17196
chore: bring back function set_cache_capacity
#17196
Conversation
set_cache_capacity
set_cache_capacity
7e4c12e
to
c64143c
Compare
c64143c
to
8f81869
Compare
8f81869
to
7580cd9
Compare
Docker Image for PR
|
Docker Image for PR
|
Is there a docs for this function? BTW: |
This is used by internal not for user. |
This function is mainly designed to help cloud operators, or in private deployment scenarios, find the right cache capacity for a given workload: balancing execution performance, query soft OOM, and spill. Once the right cache capacity is found, still need to adjust the cache size in the config to make the capacity setting persistent, ensuring it remains effective during warehouse suspend and resume operations. |
* chore:bring back func `set_cache_capacity` * test cases * revert config file * tweak test case * fix: use usize as bytes capacity * tweak lock scope * rename vars/methods of cache mgr
* chore: bring back function `set_cache_capacity` (#17196) * chore:bring back func `set_cache_capacity` * test cases * revert config file * tweak test case * fix: use usize as bytes capacity * tweak lock scope * rename vars/methods of cache mgr * resovle pick conflicts * cargo fmt * tweak audit.toml, bypass RUSTSEC-2025-0001 * pin patched opendal to tag, instead of commit hash * taplo fmt * tweak golden file of ut test_caches_table
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
bring back function
system$set_cache_capacity
(#16016)Tests
Type of change
This change is