kallithea Changeset - fb0417c65c64

Changeset - fb0417c65c64

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Mads Kiilerich - 6 years ago 2019-11-16 20:23:31
mads@kiilerich.com

Grafted from: b6f9e7904eb3

docs: document official method for beaker cache cleanup

1 file changed with 9 insertions and 0 deletions:

docs/usage/performance.rst

0 comments (0 inline, 0 general)

docs/usage/performance.rst

➞

Show inline comments

@@ @@ -14,24 +14,33 @@ Fast storage @@
 ------------
 Kallithea is often I/O bound, and hence a fast disk (SSD/SAN) and plenty of RAM
 is usually more important than a fast CPU.
 Caching
 -------
 Tweak beaker cache settings in the ini file. The actual effect of that is
 questionable.
 .. note::
     Beaker has no upper bound on cache size and will never drop any caches. For
     memory cache, the only option is to regularly restart the worker process.
     For file cache, it must be cleaned manually, as described in the `Beaker
     documentation <https://beaker.readthedocs.io/en/latest/sessions.html#removing-expired-old-sessions>`_::
         find data/cache -type f -mtime +30 -print -exec rm {} \;
 Database
 --------
 SQLite is a good option when having a small load on the system. But due to
 locking issues with SQLite, it is not recommended to use it for larger
 deployments.
 Switching to MySQL or PostgreSQL will result in an immediate performance
 increase. A tool like SQLAlchemyGrate_ can be used for migrating to another
 database platform.

0 comments (0 inline, 0 general)