##// END OF EJS Templates
Authentication: cache plugins for auth and their settings in the auth_registry....
Authentication: cache plugins for auth and their settings in the auth_registry. - Before that change on each requests 4x we loaded plugins for authentication, this hit many caches, db invalidation context and loaded the plugins logic each time. This was a heavy performance hit for SVN and other backends as they needed to load that plugins many many times - Since Authentication plugins almost never change, we'll not store the plugins listed for authentication into the authnregistry for each process - For AuthPlugins settings we now also flush plugins settings, and authnregistry cached plugins

File last commit:

r4172:0f4eef6e default
r4220:5a873939 stable
Show More
tuning-rhodecode-memory-usage.rst
26 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / system_admin / tuning / tuning-rhodecode-memory-usage.rst

RhodeCode Memory Usage

Starting from Version 4.18.X RhodeCode has a builtin memory monitor for gunicorn workers. Enabling this can limit the maximum amount of memory system can use. Each worker for RhodeCode is monitored independently. To enable Memory management make sure to have following settings inside [app:main] section of :file:`home/{user}/.rccontrol/{instance-id}/rhodecode.ini` file.

; Maximum memory usage that each worker can use before it will receive a ; graceful restart signal 0 = memory monitoring is disabled ; Examples: 268435456 (256MB), 536870912 (512MB) ; 1073741824 (1GB), 2147483648 (2GB), 4294967296 (4GB) memory_max_usage = 1073741824

; How often in seconds to check for memory usage for each gunicorn worker memory_usage_check_interval = 60

; Threshold value for which we don't recycle worker if GarbageCollection ; frees up enough resources. Before each restart we try to run GC on worker ; in case we get enough free memory after that, restart will not happen. memory_usage_recovery_threshold = 0.8