##// END OF EJS Templates
git forks were not created as bare repos
git forks were not created as bare repos

File last commit:

r2775:5d12768a beta
r2807:57456b1c beta
Show More
performance.rst
49 lines | 2.0 KiB | text/x-rst | RstLexer
Added simple docs for optimizing RhodeCode performance
r2517 .. _performance:
================================
Optimizing RhodeCode Performance
================================
docs improvements
r2775 When serving large amount of big repositories RhodeCode can start
performing slower than expected. Because of demanding nature of handling large
amount of data from version control systems here are some tips how to get
the best performance.
* RhodeCode will perform better on machines with faster disks (SSD/SAN). It's
more important to have faster disk than faster CPU.
* Slowness on initial page can be easily fixed by grouping repositories, and/or
increasing cache size (see below)
Added simple docs for optimizing RhodeCode performance
r2517
Follow these few steps to improve performance of RhodeCode system.
doc fixes
r2680 1. Increase cache
Added simple docs for optimizing RhodeCode performance
r2517
doc fixes
r2680 in the .ini file::
beaker.cache.sql_cache_long.expire=3600 <-- set this to higher number
Added simple docs for optimizing RhodeCode performance
r2517
This option affects the cache expiration time for main page. Having
few hundreds of repositories on main page can sometimes make the system
to behave slow when cache expires for all of them. Increasing `expire`
option to day (86400) or a week (604800) will improve general response
docs improvements
r2775 times for the main page. RhodeCode has an intelligent cache expiration
system and it will expire cache for repositories that had been changed.
Added simple docs for optimizing RhodeCode performance
r2517
2. Switch from sqlite to postgres or mysql
sqlite is a good option when having small load on the system. But due to
locking issues with sqlite, it's not recommended to use it for larger
setup. Switching to mysql or postgres will result in a immediate
performance increase.
3. Scale RhodeCode horizontally
- running two or more instances on the same server can speed up things a lot
- load balance using round robin or ip hash
- you need to handle consistent user session storage by switching to
db sessions, client side sessions or sharing session data folder across
instances. See http://beaker.readthedocs.org/ docs for details.
- remember that each instance needs it's own .ini file and unique
`instance_id` set in them