Merge pull request #2381 from RealRancor/redis_db_locking

Performance tuning: Recommend redis based file locking
This commit is contained in:
Carla Schroder
2016-04-25 08:21:33 -07:00
2 changed files with 9 additions and 4 deletions

View File

@@ -30,10 +30,7 @@ locking does not prevent this. Rather, it prevents simultaneous file saving.
must visit your Apps page to verify that it is disabled; the File Locking
app and Transactional File Locking cannot both operate at the same time.
When you see the warning on your ownCloud admin page "Transactional file locking
is using the database as locking backend, for best performance it's advised to
configure a memcache for locking", you are not required to use a memcache. File
locking is enabled by default, using the database locking backend. This
File locking is enabled by default, using the database locking backend. This
places a significant load on your database. Using ``memcache.locking`` relieves
the database load and improves performance. Admins of ownCloud servers with
heavy workloads should install a memcache. (See

View File

@@ -36,6 +36,14 @@ configure ownCloud for MySQL or MariaDB. If your installation is already running
SQLite then it is possible to convert to MySQL or MariaDB using the steps provided
in :doc:`../configuration_database/db_conversion`.
Using Redis-based Transactional File Locking
--------------------------------------------
File locking is enabled by default, using the database locking backend. This
places a significant load on your database. See the section
:doc:`../configuration_files/files_locking_transactional` for how to
configure ownCloud to use Redis-based Transactional File Locking.
SSL / Encryption App
--------------------