Attention
TYPO3 v11 has reached end-of-life as of October 31th 2024 and is no longer being maintained. Use the version switcher on the top left of this page to select documentation for a supported version of TYPO3.
Need more time before upgrading? You can purchase Extended Long Term Support (ELTS) for TYPO3 v11 here: TYPO3 ELTS.
Quick Start for Integrators
This section gives some simple instructions for getting started using the caching framework without giving the whole details under the hood.
Change Specific Cache Options
By default, most Core caches use the database backend. Default cache configuration
is defined in typo3/
and can be overridden in Local
.
If specific settings should be applied to the configuration, they should be added to Local
.
All settings in Local
will be merged with Default
. The easiest way to see
the final cache configuration is to use the TYPO3 backend module
System > Configuration > $GLOBALS['TYPO3_CONF_VARS']
(with installed lowlevel system extension).
Example for a configuration of redis cache backend on redis database number 42 instead of the default database backend with compression for the pages cache:
return [
// ...
'SYS' => [
// ...
'caching' => [
// ...
'cacheConfigurations' => [
// ...
'pages' => [
'backend' => \TYPO3\CMS\Core\Cache\Backend\RedisBackend::class,
'options' => [
'database' => 42,
],
],
],
],
],
];
Garbage Collection Task
Most cache backends do not have an internal system to remove old cache entries that exceeded their lifetime. A cleanup must be triggered externally to find and remove those entries, otherwise caches could grow to arbitrary size. This could lead to a slow website performance, might sum up to significant hard disk or memory usage and could render the server system unusable.
It is advised to always enable the scheduler and run the "Caching framework garbage collection" task to retain clean and small caches. This housekeeping could be done once a day when the system is otherwise mostly idle.