Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
The Advanced Cache module is collection of advanced cache strategies to help minimize load on the server, while ensuring that fresh content is served to the users. Magnolia uses Ehcache, an open course Java distributed cache. All cache data is stored in the filesystem. The Ehcache filesystem can be local to the server or network, depending on the particular configuration.
Advanced Cache is an enterprise module (3.6 and higher) included in the Enterprise Edition bundle and typically already installed. Go to Magnolia Store > Installed modules in AdminCentral to check. To install the module individually, see the general module installation instructions.
/modules/cache/config/configurations/default/cachePolicy/classback to default value
/modules/advanced-cachenode and its subnodes.
WEB-INF/liband start up Magnolia again.
The use of this strategies only make sense in cases where you have pages that take too long to load, i.e. pages that connect to backend systems.
Using this strategy, cache is not completely cleaned on content update and entries are retained. After update, when the first request comes in, fresh cache entry generation is triggered and all further requests for the same entry are served from old cache content until the new entry is ready.
Using this strategy, cache keeps a list of the most frequently served entries. The system attempts to refresh these entries as soon as it detects an update to content. All other entries are re-cached on request. It is possible to configure the number of entries to re-cache immediately and to set the lifetime of the most served content:
By default, statistics about served pages are retained indefinitely. However, you can force the system to flush the cache after each content update. To do this:
resetAfterUpdatedata node under
To change the number of pages to be eagerly re-cached:
eagerRecachedata node under
By default Magnolia waits for 10 seconds, while still serving an old version of the content, before attempting to re-cache the given entry. This timeout is controlled by the
blockingTimeout property configured in the . The
blockingTimeout applies to the whole cache factory. If you want to change the waiting time for a particular cache policy, use the
Change the waiting time for the default server and flush policies by adding a
timeout node data with value being the number of milliseconds to wait (i.e. default value is equivalent of 10 000).
Changes to cache policies and executors are applied immediately. Setting incorrect values can render the Magnolia instance inaccessible. If this happens, try the Groovy Rescue Servlet.
See also Cache module.
When content is published, the cache on the public instance is flushed to show the new content. This increases the load on the server and affects all sites in a multisite environment. You can configure multiple cache configurations to ensure that only cache entries that belong to the same subree (site) as the published content are flushed.
First, configure cache filter bypasses in
/server/filters/cache to ensure that the site-specific filter listens only for changes on the defined subtree, while the default configuration listens for everything else. Everything except the requests handled by the subtree is cached.
Here's an example configuration for
Next, configure multiple cache configurations in
mxin the example above).
extendsproperty and set the value to
/default/flushPolicy/policies/flushAll/classreplace FlushAllListeningPolicy with SiteAwareFlushAllListeningPolicy .