Page History
...
Caching arbitrary objects
...
Magnolia cache uses established third-party libraries for the low level functions. Depending on your production environment, one cache implementation may fit better than another. Please Please contact Magnolia Services to get the the best cache strategy for your project and server setup.
| Anchor | ||||
|---|---|---|---|---|
|
By default Magnolia uses Ehcache. The third party library comes with and is configured with Magnolia Ehcache module 3 module.
Ehcache version update to 2.10
Cache module version 5.4 (bundled with Magnolia 5.4) updated Ehcache from 1.5 to 2.10.
Ehcache is a robust, proven and full-featured cache product which has made it the most widely-used Java cache. It provides off-heap storage capabilities and is full compatibility with javax.cache API (JSR-107).
Ehcache 3.x always keeps cached content Ehcache stores cached content to disk. On version 1.5, cached content was always kept on the disk as long as flushing was is not proactively requested. Version 2.10 deletes cached items when the server is stopped. As a consequence, when you restart the server, the cache store must be rebuilt again. Since a production system is stopped rarely the loss of the persistent cache store is typically not a problem. A production server is typically stopped only when updating Magnolia or if the server crashes.However, if you want to use a cache that will persist between restarts of Magnolia, use the Memcached implementationCached content is also retained if you must restart the system.
Alternative implementation - Memcached
...
Overview
Content Tools