#110932Bad Extbase persistence performance in BE due to storagePid calculation
Description
Extbase persistance has a severe performance problem in backend context due to storagePid configuration calculation.
If `recursive > 0` the core performs rootline walks and permissions checks within the BackendConfigurationManager
Since there is no caching in place, this happens for every new Query object.
Fix this by adding caching layer in the `ConfigurationManager` like there is for frontend already.
Reviews 2
History 14
-
Gerrit Code Review pushed patch set 1 for main to change 96416 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-06T14:41:32+00:00" > 10/06/26, 14:41 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 96637 <span data-processor="relativetime" data-value="2026-10-12T18:37:48+00:00" > 10/12/26, 18:37 </span>
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 96637 <span data-processor="relativetime" data-value="2026-10-12T18:53:15+00:00" > 10/12/26, 18:53 </span>
-
Johannes Kasberger commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-12T19:10:09+00:00" > 10/12/26, 19:10 </span>
Applied in changeset commit:9b1f4de37904193b1e6d5128c58b0fb71b86f51e.