Review main Merged

96416[TASK] Cache backend configuration in Extbase ConfigurationManager

Markus Klein CR +2 V +2 Normal +174 −5 updated 10/12/26, 19:08

Commit message

In backend context the ConfigurationManager resolves the framework
configuration from scratch on every call. QueryFactory::create() fetches
it for each query, which includes every lazily loaded relation via
DataMapper::getPreparedQuery(). With "persistence.recursive" configured,
each of these calls walks the page tree again with one query on "pages"
per visited page - and for relations the result is discarded right away,
since DataMapper disables respectStoragePage on these queries.

In a backend module listing 10 records with ~80 lazily loaded relations
this caused 299 of 606 queries. The frontend branch already caches the
configuration per extension and plugin.

The resolved backend configuration is now cached as well. The cache is
indexed by the explicitly requested extension and plugin name, as these
select a different plugin configuration (and thus persistence settings).
It is reset when the plugin configuration changes via setConfiguration(),
and is only used for the request and backend user it was built with,
since these determine the TypoScript and the page permissions applied
to the recursive storage pid lookup.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
    • Benni Mack +1
  • Verified V +2 Done
    • Georg Ringer +2
    • Benni Mack +1
    • core-ci +1 CI

Issues 1

Files 3

Review log 45

  1. Markus Klein uploaded patch set 1 10/06/26, 14:41

  2. core-ci voted on patch set 1 V +1 10/06/26, 14:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/110230

  3. Benni Mack voted on patch set 1 CR +1 V +1 10/07/26, 10:39

  4. Georg Ringer voted on patch set 1 CR +2 V +2 10/12/26, 19:08

  5. Georg Ringer merged patch set 2 10/12/26, 19:08