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

Fixup autotuning sample config #12760

Closed
wants to merge 3 commits into from

Conversation

erikjohnston
Copy link
Member

This was added in #12701

@erikjohnston erikjohnston marked this pull request as ready for review May 17, 2022 11:01
@erikjohnston erikjohnston requested a review from a team as a code owner May 17, 2022 11:01
# `target_cache_memory_usage`, `min_cache_ttl`. These flags work in conjunction with each other to maintain
# a balance between cache memory usage and cache entry availability. You must be using jemalloc to utilize
# this option, and all three of the options must be specified for this feature to work.
# This flag enables cache autotuning, and is further specified by the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to me, "flag" is a boolean. None of these things are flags? Not a major problem though.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/flag/setting/ would be better, I think

Comment on lines +795 to 814
# This flag sets a ceiling on much memory the cache can use before
# caches begin to be continuously evicted. They will continue to be
# evicted until the memory usage drops below the
# `target_memory_usage`, set in the flag below, or until the
# `min_cache_ttl` is hit.
#
#max_cache_memory_usage: 1024M

# This flag sets a rough target for the desired memory usage of the caches.
# This flag sets a rough target for the desired memory usage of the
# caches.
#
#target_cache_memory_usage: 758M

# 'min_cache_ttl` sets a limit under which newer cache entries are not evicted and is only applied when
# caches are actively being evicted/`max_cache_memory_usage` has been exceeded. This is to protect hot caches
# from being emptied while Synapse is evicting due to memory.
# 'min_cache_ttl` sets a limit under which newer cache entries are not
# evicted and is only applied when caches are actively being
# evicted/`max_cache_memory_usage` has been exceeded. This is to
# protect hot caches from being emptied while Synapse is evicting due
# to memory.
#
#min_cache_ttl: 5m
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are the defaults for these things? (what happens if they are not set?) (also needs adding to the config manual I think)

# evicted until the memory usage drops below the
# `target_memory_usage`, set in the flag below, or until the
# `min_cache_ttl` is hit.
#
#max_cache_memory_usage: 1024M
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please could you document, here and in the config manual, what the valid suffixes are, and what they mean? (is M 1000000 or 1048576 ?)

@H-Shay
Copy link
Contributor

H-Shay commented May 17, 2022

I can fix all this in the config manual, as it was on my agenda to rip out the config comments today anyway.

@H-Shay
Copy link
Contributor

H-Shay commented May 18, 2022

The issues have hopefully been addressed here: #12776

I would say that this should be closed as I am in the process of deleting all comments from the config file as we speak.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants