#108615DatabaseRowsUpdateWizard is so slow
Description
DatabaseRowsUpdateWizard is so slow
It’s because the script spends 80% of its time introspecting the database schema, at every insert/update sql query.
This is because of \TYPO3\CMS\Core\Database\Schema\SchemaInformation::introspectTable and its cache: the cache backend is NullBackend, so the db schema is introspected ever and ever.
I don’t know why the CacheManager is injected with caching disabled: maybe because its CLI or whatever “install tool” context.
I “fixed” this performance issue by adding a static cache array in \TYPO3\CMS\Core\Database\Schema\SchemaInformation::introspectTable.
The performance of this update wizard was drasticaly improved.
Reviews 2
Related issues 2
History 4
-
Stefan Bürk changed Related to #107610 <span data-processor="relativetime" data-value="2026-01-10T22:19:12+00:00" > 01/10/26, 22:19 </span>
-
Stefan Bürk commented and changed category assigned to Stefan Bürk <span data-processor="relativetime" data-value="2026-01-10T22:34:28+00:00" > 01/10/26, 22:34 </span>
-
Stefan Bürk changed Related to #107546 <span data-processor="relativetime" data-value="2026-01-10T22:35:45+00:00" > 01/10/26, 22:35 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-13T08:56:34+00:00" > 11/13/26, 08:56 </span>I am closing this due to the fix in v13+ in #107610
Thanks @dogawaf for reporting this.
The schema information handling has been restructured in main (v14) and v13
by a couple of changes, mainly introducing own classes better serializable,
because the doctrine/dbal classes (Types) wasn’t compatible with it and the
series ended introducing a additional runtime cache as first level cache in
the SchemaInformation handling [1].
> I don’t know why the CacheManager is injected with caching disabled:
> maybe because its CLI or whatever “install tool” context.
Upgrade wizards(command) operates in failsafe mode with partly evaluated
context, but does not recover all caches. For the install context cache
configuration are overriden/reconfigured with NullBackend except a small
list, for example the DI cache is kept in place and not reconfigured to
NullBackend.
That’s intended and should be kept, and using the Runtime cache would help
as this cache is also not reconfigured with NullBackend and is the better
alternative than using static property cache(s) on classes.
> I “fixed” this performance issue by adding a static cache array
> in \TYPO3\CMS\Core\Database\Schema\SchemaInformation::introspectTable.
Static property caches are evil and we worked and still working very hard
to get rid of them, because no-one really knows where they are sitting and
reseting is a huge effort to get right, for example in testing (testing-framework)
or sub-requests or long-running processes (commands, daemon like worker, …).
The [1] change cannot be simply applied to TYPO3 v12 based on the fact that
the change has been made after the already mentioned series of changes, mainly
the cache handling streamlining change [2], which has been considered to be
to heavy for long time LTS v12 and not backported down to it. Main reason was,
that the area it revealed main cache issues was not that of high priority and
the risk assessment was that the danger of breaking something was higher than
the fix.
The mentioned issue described here was not on the paper back then, and to be
honest I don’t think it would have changed the decision for [2].
For your “local” fix I would suggest that you have a look into change [1] and
adopt the runtime cache instead of a static property cache. I’ll try to evaluate
if we can make the [2] backport (adopted) at all, and in case we going to make
it, as late backport with adoption or as dedicated change using the issue number
of this issue.
Don’t get me wrong – not yet saying that we decline it or accept it, just wanted
to give some early feedback on this and mentioning at least danger of the static
property chace implemented in your local fix.