[BUGFIX] Faster garbage collection of caching framework 54/33254/10
authorStephan Großberndt <stephan@grossberndt.de>
Fri, 10 Oct 2014 22:03:31 +0000 (00:03 +0200)
committerChristian Kuhn <lolli@schwarzbu.ch>
Mon, 19 Jan 2015 15:18:02 +0000 (16:18 +0100)
commit2732b605f17a332c211185f2ecf8979e604ddd8b
tree63da50cc604f7d7a3addbf9799ebac2758bd41a3
parentbcbcd4c6fefad3cdf7ee7cc6f647f6563981a7a8
[BUGFIX] Faster garbage collection of caching framework

Do the garbage collection of the caching framework with a single DELETE
statement using JOIN instead of fetching all entries by identifier and
deleting them in a separate statement afterwards. This improves
performance especially for big installations.

For EXT:DBAL the old behaviour is kept since Oracle does neither
support subqueries nor DELETE statements with JOINs.

Removed test collectGarbageSelectsExpiredCacheEntries since
collectGarbage() doesn't perform a SELECT query anymore.

Resolves: #61814
Releases: master, 6.2
Change-Id: Ifca9065e274b85219ca81afa87724ce8884cc662
Reviewed-on: http://review.typo3.org/33254
Reviewed-by: Stephan Großberndt <stephan@grossberndt.de>
Reviewed-by: Stefan Neufeind <typo3.neufeind@speedpartner.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
typo3/sysext/core/Classes/Cache/Backend/Typo3DatabaseBackend.php
typo3/sysext/core/Tests/Unit/Cache/Backend/Typo3DatabaseBackendTest.php