From 90f1543da8996a0c3b49313cb319690c812278f0 Mon Sep 17 00:00:00 2001 From: Christoph Wurst Date: Thu, 1 Feb 2024 18:31:00 +0100 Subject: [PATCH] fix(devmanual): Move cached data out of database performance section Signed-off-by: Christoph Wurst --- developer_manual/digging_deeper/performance.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/developer_manual/digging_deeper/performance.rst b/developer_manual/digging_deeper/performance.rst index b606601da..f235d8211 100644 --- a/developer_manual/digging_deeper/performance.rst +++ b/developer_manual/digging_deeper/performance.rst @@ -106,11 +106,6 @@ Transactions are crucial for changes that belong together but they can cause pro Look out for messages like ``Transaction took longer than 1s: 7.1270351409912`` and ``Transaction rollback took longer than 1s: 1.2153599501``. -Cached data -^^^^^^^^^^^ - -Starting from Nextcloud 26, user and group display names now are cached. Use the ``IUserManager::getDisplayName`` or ``IGroupManager::getDisplayName`` functions to avoid roundtrips to the database. - Measuring performance ^^^^^^^^^^^^^^^^^^^^^ @@ -118,6 +113,11 @@ If you do bigger changes in the architecture or the database structure you shoul The recommendation is to automatically do 10000 PROPFINDs or file uploads, measure the time and compare the time before and after the change. +Cached data +----------- + +Starting from Nextcloud 26, user and group display names now are cached. Use the ``IUserManager::getDisplayName`` or ``IGroupManager::getDisplayName`` functions to avoid roundtrips to the database. + Getting help ------------