You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/usage/configuration/config_documentation.md
+15-2
Original file line number
Diff line number
Diff line change
@@ -1119,16 +1119,29 @@ Caching can be configured through the following sub-options:
1119
1119
with intermittent connections, at the cost of higher memory usage.
1120
1120
By default, this is zero, which means that sync responses are not cached
1121
1121
at all.
1122
-
1122
+
* `cache_autotuning` and its sub-options `max_cache_memory_usage`, `target_cache_memory_usage`, and
1123
+
`min_cache_ttl`work in conjunction with each other to maintain a balance between cache memory
1124
+
usage and cache entry availability. You must be using [jemalloc](https://github.com/matrix-org/synapse#help-synapse-is-slow-and-eats-all-my-ramcpu)
1125
+
to utilize this option, and all three of the options must be specified for this feature to work.
1126
+
* `max_cache_memory_usage` sets a ceiling on how much memory the cache can use before caches begin to be continuously evicted.
1127
+
They will continue to be evicted until the memory usage drops below the `target_memory_usage`, set in
1128
+
the flag below, or until the `min_cache_ttl` is hit.
1129
+
* `target_memory_usage` sets a rough target for the desired memory usage of the caches.
1130
+
* `min_cache_ttl` sets a limit under which newer cache entries are not evicted and is only applied when
1131
+
caches are actively being evicted/`max_cache_memory_usage` has been exceeded. This is to protect hot caches
1132
+
from being emptied while Synapse is evicting due to memory.
0 commit comments