diff options
author | Aaron Raimist <aaron@raim.ist> | 2020-07-29 09:35:44 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-07-29 10:35:44 -0400 |
commit | 2184f61faeb5ce88c05d28913e3f881813c0c5dd (patch) | |
tree | d4bda7da6465c1087cab52b46053d4e65e94f25a /debian/synctl.ronn | |
parent | Convert storage layer to async/await. (#7963) (diff) | |
download | synapse-2184f61faeb5ce88c05d28913e3f881813c0c5dd.tar.xz |
Various improvements to the docs (#7899)
Diffstat (limited to 'debian/synctl.ronn')
-rw-r--r-- | debian/synctl.ronn | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/debian/synctl.ronn b/debian/synctl.ronn index a73c832f62..1bad6094f3 100644 --- a/debian/synctl.ronn +++ b/debian/synctl.ronn @@ -46,19 +46,20 @@ Configuration file may be generated as follows: ## ENVIRONMENT * `SYNAPSE_CACHE_FACTOR`: - Synapse's architecture is quite RAM hungry currently - a lot of - recent room data and metadata is deliberately cached in RAM in - order to speed up common requests. This will be improved in - future, but for now the easiest way to either reduce the RAM usage - (at the risk of slowing things down) is to set the - SYNAPSE_CACHE_FACTOR environment variable. Roughly speaking, a - SYNAPSE_CACHE_FACTOR of 1.0 will max out at around 3-4GB of - resident memory - this is what we currently run the matrix.org - on. The default setting is currently 0.1, which is probably around - a ~700MB footprint. You can dial it down further to 0.02 if - desired, which targets roughly ~512MB. Conversely you can dial it - up if you need performance for lots of users and have a box with a - lot of RAM. + Synapse's architecture is quite RAM hungry currently - we deliberately + cache a lot of recent room data and metadata in RAM in order to speed up + common requests. We'll improve this in the future, but for now the easiest + way to either reduce the RAM usage (at the risk of slowing things down) + is to set the almost-undocumented ``SYNAPSE_CACHE_FACTOR`` environment + variable. The default is 0.5, which can be decreased to reduce RAM usage + in memory constrained enviroments, or increased if performance starts to + degrade. + + However, degraded performance due to a low cache factor, common on + machines with slow disks, often leads to explosions in memory use due + backlogged requests. In this case, reducing the cache factor will make + things worse. Instead, try increasing it drastically. 2.0 is a good + starting value. ## COPYRIGHT |