Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Commit 046320b

Browse files
authored
Fix missing word in autotune sub-option description (#14674)
Fix `target_memory_usage` being used in the description for the actual `cache_autotune` sub-option `target_cache_memory_usage`. Signed-off-by: Jeremy Kescher <[email protected]> Signed-off-by: Jeremy Kescher <[email protected]>
1 parent 4f4d690 commit 046320b

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

changelog.d/14674.doc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Fix `target_memory_usage` being used in the description for the actual `cache_autotune` sub-option `target_cache_memory_usage`.

docs/usage/configuration/config_documentation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1148,7 +1148,7 @@ number of entries that can be stored.
11481148
* `max_cache_memory_usage` sets a ceiling on how much memory the cache can use before caches begin to be continuously evicted.
11491149
They will continue to be evicted until the memory usage drops below the `target_memory_usage`, set in
11501150
the setting below, or until the `min_cache_ttl` is hit. There is no default value for this option.
1151-
* `target_memory_usage` sets a rough target for the desired memory usage of the caches. There is no default value
1151+
* `target_cache_memory_usage` sets a rough target for the desired memory usage of the caches. There is no default value
11521152
for this option.
11531153
* `min_cache_ttl` sets a limit under which newer cache entries are not evicted and is only applied when
11541154
caches are actively being evicted/`max_cache_memory_usage` has been exceeded. This is to protect hot caches

0 commit comments

Comments
 (0)