Mercurial > kallithea
view docs/usage/performance.rst @ 4546:805ec49152c9
simplehg: don't quiet Hg output for push
I want to be able to see informational messages from e.g. the Hg Bugzilla
extension.
Here's output without the patch. This is identical to the output produced if
the Bugzilla extension is disabled:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
and with the patch:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
remote: bug 3270 already knows about changeset 6c03abbabb46
The last line indicates that the Bugzilla bug text already contains an entry
for that changeset. It's produced by a call to self.ui.status() in the
extension.
I think the point here is that the deleted code is ensuring that the remote hg
(i.e. the Kallithea hg) always runs with the --quiet flag when receiving a
push. This seems an arbitrary decision to me, and one that removes potentially
useful information from the output. I believe this behaviour is different to
that seen by the user if pushing to hgweb (I've not tried it, but inspected the
hgweb source for setting quiet) and is certainly different to pushing over ssh.
author | Jim Hague <jim.hague@acm.org> |
---|---|
date | Thu, 17 Jul 2014 12:47:56 +0100 |
parents | e73a69cb98dc |
children | 4e6dfdb3fa01 |
line wrap: on
line source
.. _performance: ================================ Optimizing Kallithea Performance ================================ When serving large amount of big repositories Kallithea 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. * Kallithea 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), that includes using lightweight dashboard option and vcs_full_cache setting in .ini file Follow these few steps to improve performance of Kallithea system. 1. Increase cache in the .ini file:: beaker.cache.sql_cache_long.expire=3600 <-- set this to higher number 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 times for the main page. Kallithea has an intelligent cache expiration system and it will expire cache for repositories that had been changed. 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 Kallithea horizontally Scaling horizontally can give huge performance increase when dealing with large traffic (large amount of users, CI servers etc). Kallithea can be scaled horizontally on one (recommended) or multiple machines. In order to scale horizontally you need to do the following: - each instance needs it's own .ini file and unique `instance_id` set in them - each instance `data` storage needs to be configured to be stored on a shared disk storage, preferably together with repositories. This `data` dir contains template caches, sessions, whoosh index and it's used for tasks locking (so it's safe across multiple instances). Set the `cache_dir`, `index_dir`, `beaker.cache.data_dir`, `beaker.cache.lock_dir` variables in each .ini file to shared location across Kallithea instances - if celery is used each instance should run separate celery instance, but the message broken should be common to all of them (ex one rabbitmq shared server) - load balance using round robin or ip hash, recommended is writing LB rules that will separate regular user traffic from automated processes like CI servers or build bots.