kallithea Changeset - d442d8395b75

Changeset - d442d8395b75

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Thomas De Schampheleire - 6 years ago 2020-08-22 21:22:51
thomas.de_schampheleire@nokia.com

docs: reduce double nesting level in performance.rst

Rendered text was too far to the right.

1 file changed with 12 insertions and 12 deletions:

docs/usage/performance.rst

0 comments (0 inline, 0 general)

docs/usage/performance.rst

➞

Show inline comments

@@ @@ -58,36 +58,36 @@ speed. It is thus a good idea to run mul @@
     Kallithea and the embedded Mercurial backend are not thread-safe. Each
     worker process must thus be single-threaded.
 Web servers can usually launch multiple worker processes - for example ``mod_wsgi`` with the
 ``WSGIDaemonProcess`` ``processes`` parameter or ``uWSGI`` or ``gunicorn`` with
 their ``workers`` setting.
 Kallithea can also be scaled horizontally across multiple machines.
 In order to scale horizontally on multiple machines, you need to do the
 following:
     - Each instance's ``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 is used for
       task locking (so it is safe across multiple instances). Set the
       ``cache_dir``, ``index_dir``, ``beaker.cache.data_dir``, ``beaker.cache.lock_dir``
       variables in each .ini file to a shared location across Kallithea instances
     - If using several Celery instances,
       the message broker should be common to all of them (e.g.,  one
       shared RabbitMQ 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.
 - Each instance's ``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 is used for
   task locking (so it is safe across multiple instances). Set the
   ``cache_dir``, ``index_dir``, ``beaker.cache.data_dir``, ``beaker.cache.lock_dir``
   variables in each .ini file to a shared location across Kallithea instances
 - If using several Celery instances,
   the message broker should be common to all of them (e.g.,  one
   shared RabbitMQ 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.
 Serve static files directly from the web server
 -----------------------------------------------
 With the default ``static_files`` ini setting, the Kallithea WSGI application
 will take care of serving the static files from ``kallithea/public/`` at the
 root of the application URL.
 The actual serving of the static files is very fast and unlikely to be a
 problem in a Kallithea setup - the responses generated by Kallithea from
 database and repository content will take significantly more time and

0 comments (0 inline, 0 general)