From 3ef7cc9427ece01723eb8629fa83db2e6bef17c5 Mon Sep 17 00:00:00 2001 From: Carla Schroder Date: Wed, 7 Oct 2015 06:56:34 -0700 Subject: [PATCH 1/2] add note re memcache locking --- .../configuration_files/files_locking_transactional.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/admin_manual/configuration_files/files_locking_transactional.rst b/admin_manual/configuration_files/files_locking_transactional.rst index 083aa5d80..7b14cc5a8 100644 --- a/admin_manual/configuration_files/files_locking_transactional.rst +++ b/admin_manual/configuration_files/files_locking_transactional.rst @@ -5,7 +5,7 @@ Transactional File Locking ownCloud's new transactional file locking mechanism operates differently than the old File Locking application, and will eventually replace it. The purpose of this mechanism is to avoid file corruption during normal operation. If you -select to use the new file locking mechanism make sure you disable the File +elect to use the new file locking mechanism make sure you disable the File Locking app. The new file locking mechanism has these capabilities: @@ -34,6 +34,12 @@ file like this example:: 'port' => 6379, 'timeout' => 0.0, ), + +.. note:: Large installations especially benefit from setting + ``memcache.locking``. File locking is enable by default, which uses the + database locking backend. This places a significant load on your database. + Using ``memcache.locking`` relieves the database load and improves + performance. The **Server status** section on your ownCloud Admin page indicates whether experimental file locking is enabled or disabled. From 54415a737f971b29541f13f0606e0274b3ea7756 Mon Sep 17 00:00:00 2001 From: Carla Schroder Date: Wed, 7 Oct 2015 11:25:28 -0700 Subject: [PATCH 2/2] Update files_locking_transactional.rst --- .../configuration_files/files_locking_transactional.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin_manual/configuration_files/files_locking_transactional.rst b/admin_manual/configuration_files/files_locking_transactional.rst index 7b14cc5a8..fca3c476b 100644 --- a/admin_manual/configuration_files/files_locking_transactional.rst +++ b/admin_manual/configuration_files/files_locking_transactional.rst @@ -36,7 +36,7 @@ file like this example:: ), .. note:: Large installations especially benefit from setting - ``memcache.locking``. File locking is enable by default, which uses the + ``memcache.locking``. File locking is enabled by default, which uses the database locking backend. This places a significant load on your database. Using ``memcache.locking`` relieves the database load and improves performance.