Show More
@@ -47,7 +47,7 b' the ``debug`` level.' | |||||
47 | ### LOGGING CONFIGURATION #### |
|
47 | ### LOGGING CONFIGURATION #### | |
48 | ################################ |
|
48 | ################################ | |
49 | [loggers] |
|
49 | [loggers] | |
50 |
keys = root, sqlalchemy, |
|
50 | keys = root, sqlalchemy, rhodecode, ssh_wrapper | |
51 |
|
51 | |||
52 | [handlers] |
|
52 | [handlers] | |
53 | keys = console, console_sql, file, file_rotating |
|
53 | keys = console, console_sql, file, file_rotating | |
@@ -69,12 +69,6 b' the ``debug`` level.' | |||||
69 | ## "level = DEBUG" logs the route matched and routing variables. |
|
69 | ## "level = DEBUG" logs the route matched and routing variables. | |
70 | propagate = 1 |
|
70 | propagate = 1 | |
71 |
|
71 | |||
72 | [logger_beaker] |
|
|||
73 | level = DEBUG |
|
|||
74 | handlers = |
|
|||
75 | qualname = beaker.container |
|
|||
76 | propagate = 1 |
|
|||
77 |
|
||||
78 | [logger_rhodecode] |
|
72 | [logger_rhodecode] | |
79 | level = DEBUG |
|
73 | level = DEBUG | |
80 | handlers = |
|
74 | handlers = |
@@ -113,33 +113,33 b' match, for example:' | |||||
113 | VCS Server Memory Optimization |
|
113 | VCS Server Memory Optimization | |
114 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
|
114 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
115 |
|
115 | |||
116 |
To |
|
116 | To optimize the VCS server to manage the cache and memory usage efficiently, you need to | |
117 | configure the following options in the |
|
117 | configure the following options in the | |
118 | :file:`/home/{user}/.rccontrol/{vcsserver-id}/vcsserver.ini` file. Once |
|
118 | :file:`/home/{user}/.rccontrol/{vcsserver-id}/vcsserver.ini` file. Once | |
119 | configured, restart the VCS Server. |
|
119 | configured, restart the VCS Server. By default we use an optimal settings, but in certain | |
|
120 | conditions tunning expiration_time and max_size can affect memory usage and performance | |||
120 |
|
121 | |||
121 | .. rst-class:: dl-horizontal |
|
122 | .. code-block:: ini | |
122 |
|
|
123 | ||
123 | \beaker.cache.repo_object.type = memorylru |
|
124 | ## cache region for storing repo_objects cache | |
124 | Configures the cache to discard the least recently used items. |
|
125 | rc_cache.repo_object.backend = dogpile.cache.rc.memory_lru | |
125 | This setting takes the following valid options: |
|
126 | ||
|
127 | ## cache auto-expires after N seconds, setting this to 0 disabled cache | |||
|
128 | rc_cache.repo_object.expiration_time = 300 | |||
126 |
|
|
129 | ||
127 | * ``memorylru``: The default setting, which removes the least recently |
|
130 | ## max size of LRU, old values will be discarded if the size of cache reaches max_size | |
128 | used items from the cache. |
|
131 | ## Sets the maximum number of items stored in the cache, before the cache | |
129 | * ``memory``: Runs the VCS Server without clearing the cache. |
|
132 | ## starts to be cleared. | |
130 | * ``nocache``: Runs the VCS Server without a cache. This will |
|
|||
131 | dramatically reduce the VCS Server performance. |
|
|||
132 |
|
|
133 | ||
133 | \beaker.cache.repo_object.max_items = 100 |
|
134 | ## As a general rule of thumb, running this value at 120 resulted in a | |
134 | Sets the maximum number of items stored in the cache, before the cache |
|
135 | ## 5GB cache. Running it at 240 resulted in a 9GB cache. Your results | |
135 | starts to be cleared. |
|
136 | ## will differ based on usage patterns and |repo| sizes. | |
136 |
|
|
137 | ||
137 | As a general rule of thumb, running this value at 120 resulted in a |
|
138 | ## Tweaking this value to run at a fairly constant memory load on your | |
138 | 5GB cache. Running it at 240 resulted in a 9GB cache. Your results |
|
139 | ## server will help performance. | |
139 | will differ based on usage patterns and |repo| sizes. |
|
|||
140 |
|
|
140 | ||
141 | Tweaking this value to run at a fairly constant memory load on your |
|
141 | rc_cache.repo_object.max_size = 120 | |
142 | server will help performance. |
|
142 | ||
143 |
|
|
143 | ||
144 | To clear the cache completely, you can restart the VCS Server. |
|
144 | To clear the cache completely, you can restart the VCS Server. | |
145 |
|
145 |
General Comments 0
You need to be logged in to leave comments.
Login now