Task #81500
closed
Story #81432: Replace TYPO3 caching solution with PSR-6 / Doctrine capable alternative
Switch to filesystem caches as default
0%
Description
As explained on https://gist.github.com/NamelessCoder/6519f8a0e05dbc4613de16c07bb63a6d using a filesystem based cache as default would benefit our most common use cases and is unlikely to present an actual problem for enterprise-level setups which use multi-slave rendering and have tried and failed horribly to use DB for cache backend. The engines are datatype-compatible so the only difference is in where the data gets stored.
Updated by
Updated by Susanne Moog about 4 years ago
- Status changed from New to Closed
Hey Claus,
closing here as we - for the reasons you gave - now have new cache presets explaining the circumstances on when to use what and providing an easy way to choose the correct one:
"Storing the caches in the database is usually the best choice for standard environments as well as for installations where a network file system (NFS) is used and file system access impacts the performance and should be avoided (high disk I/O).
The file-based storage for TYPO3 caches is more efficient in shared hosting environments or if a distributed database is used.
For more complex, high-end installations, memory-based caches such as Redis or Memcached should be considered which require additional configuration in "LocalConfiguration.php". "
I think this is enough (especially as changing defaults has its own impact and upgrade path problems).
If you think this should be done anyway, you can of course reopen it to work on it :)