rhodecode-enterprise-ce Files · docs/admin/system_admin/tuning/tuning-vcs-server-memory-usage.rst

d-cache: don't init in includeme so we don't trigger s3 connections on startup of rcstack....

d-cache: don't init in includeme so we don't trigger s3 connections on startup of rcstack. The d-cache will be initied only when needed during first file download

dan - - Load All Authors

File last commit:

r4172:0f4eef6e default


                r5487:c594e70d

default

Download file

             tuning-vcs-server-memory-usage.rst
        
                    26 lines
            
             | 1.1 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / admin / system_admin / tuning / tuning-vcs-server-memory-usage.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        dan
    
docs: updated performance/tunning docs according to latest code changes

              r4172
            
      .. _adjust-vcs-server-mem:

      VCSServer 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 VCS Server is monitored independently.

      To enable Memory management make sure to have following settings inside `[app:main] section` of

      :file:`home/{user}/.rccontrol/{instance-id}/vcsserver.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

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

dan docs: updated performance/tunning docs according to latest code changes	r4172	.. _adjust-vcs-server-mem:

		VCSServer 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 VCS Server is monitored independently.
		To enable Memory management make sure to have following settings inside `[app:main] section` of
		:file:`home/{user}/.rccontrol/{instance-id}/vcsserver.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