Mercurial > kallithea

comparison docs/usage/performance.rst @ 3224:8b8edfc25856 beta

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
whitespace cleanup
author Marcin Kuzminski <marcin@python-works.com>
date Fri, 25 Jan 2013 02:31:17 +0100
parents 5d12768a0aa1
children 4cd84f4f28fb
comparison
equal deleted inserted replaced
3223:74e455c06881 3224:8b8edfc25856
20 20
21 21
22 1. Increase cache 22 1. Increase cache
23 23
24 in the .ini file:: 24 in the .ini file::
25 25
26 beaker.cache.sql_cache_long.expire=3600 <-- set this to higher number 26 beaker.cache.sql_cache_long.expire=3600 <-- set this to higher number
27 27
28 This option affects the cache expiration time for main page. Having 28 This option affects the cache expiration time for main page. Having
29 few hundreds of repositories on main page can sometimes make the system 29 few hundreds of repositories on main page can sometimes make the system
30 to behave slow when cache expires for all of them. Increasing `expire` 30 to behave slow when cache expires for all of them. Increasing `expire`
31 option to day (86400) or a week (604800) will improve general response 31 option to day (86400) or a week (604800) will improve general response
32 times for the main page. RhodeCode has an intelligent cache expiration 32 times for the main page. RhodeCode has an intelligent cache expiration
33 system and it will expire cache for repositories that had been changed. 33 system and it will expire cache for repositories that had been changed.
34 34
35 2. Switch from sqlite to postgres or mysql 35 2. Switch from sqlite to postgres or mysql
36 36
37 sqlite is a good option when having small load on the system. But due to 37 sqlite is a good option when having small load on the system. But due to
38 locking issues with sqlite, it's not recommended to use it for larger 38 locking issues with sqlite, it's not recommended to use it for larger
39 setup. Switching to mysql or postgres will result in a immediate 39 setup. Switching to mysql or postgres will result in a immediate
40 performance increase. 40 performance increase.
41 41
42 3. Scale RhodeCode horizontally 42 3. Scale RhodeCode horizontally
43 43
44 - running two or more instances on the same server can speed up things a lot 44 - running two or more instances on the same server can speed up things a lot
45 - load balance using round robin or ip hash 45 - load balance using round robin or ip hash
46 - you need to handle consistent user session storage by switching to 46 - you need to handle consistent user session storage by switching to
47 db sessions, client side sessions or sharing session data folder across 47 db sessions, client side sessions or sharing session data folder across
48 instances. See http://beaker.readthedocs.org/ docs for details. 48 instances. See http://beaker.readthedocs.org/ docs for details.
49 - remember that each instance needs it's own .ini file and unique 49 - remember that each instance needs it's own .ini file and unique
50 `instance_id` set in them 50 `instance_id` set in them