fix(devmanual): Move cached data out of database performance section

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
This commit is contained in:
Christoph Wurst
2024-02-01 18:31:00 +01:00
committed by MichaIng
parent ef0d415554
commit 90f1543da8

View File

@@ -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
------------