There are few things you need to be aware of while playing with different cache configurations. Since 3.6 we try to make maximum use of all caching facilities available. So not only does Magnolia caches the pages it served, it also tries to advice the browser about the content it requested so the browser itself can use its cache properly.
By default browser cache configuration is set to tell browser to keep the content in local cache for 30 minutes. (see /modules/cache/config/configurations/default/browserCachePolicy/expirationMinutes) If you want to disable this all together, you can change executor for browserCachePolicy from info...Fixed to info...Never Now for the server cache itself the default policy is to flush all the content as soon as activation of piece of content is finished. That means any request for content coming after such event has to go to the repo and generate whole page incl. all the images and whatever else has to be on the page. Such behavior ensures user gets the new version of content asap, on the other hand it creates higher load on server and slower responses to content requests after every time something gets activated. To avoid that since 3.6 you can write your own caching & flushing policy to tweak this to minimize impact on the users. By default we provide some strategies which we thought might be useful to avoid such high load situations. One of them is EagerRecachePolicy. This policy postpones flushing of the old cache until it eagerly re-caches most often served items. Until re-caching is finished old content is served to all users by cache. So the benefit here is that once the cache is flushed, most often served items (according to cache statistics) are already r-ecached and whatever new pages needs to be put to cache are those not so often served. To summarize what I tried to explain above: with Eager Rec-aching, user sees new content actually later rather then sooner, but chances are that the content such user asks for will be already re-cached and therefore served quickly with minimal use of server resources. Otherwise setting cache and flush policies should be enough to make it work. HTH, Jan On Tue, 2008-08-12 at 11:08 -0400, Po Ki Chui wrote: > Hi all, > > From http://documentation.magnolia.info/modules/advanced-cache.html, > I've changed my cache and flush policy to the Eager re-caching > strategy. However, after an activation with some content change, it's > still showing the old content. Besides changing the policy classes, > does anyone know what else I need to configure? > > > > Thanks, > Po Ki > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/ > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
