Let's keep those cache entries for little bit longer

Have you got magnolia-4.3? Setup multiple sites? All right, you are all done. The only thing left is to observe the load on the server and how many requests you can serve. You might have noticed that after activating the content, load on the public is bit higher even though there is no increase in traffic. Why? Simply because after activating the piece of content, cache on the public instance have been flushed. Well, so far this is actually nothing else but what you want. You activated new content and you indeed want to show world what is there and not the stale old stuff. Never the less, when using multiple sites, you might have also noticed that you are getting the hit also for the other sites then the one for which you activated the content. And in most cases, this is completely unnecessary since each site has own content and changes to one site do not affect the other. So how to get out of this bind? If you dig bit into the way cache works (which you might do by reading older entries here and the official documentation), the obvious solution you will most likely come up with is to write a custom flush policy and when new content is activated, clear from the cache only those entries that belong to the same subtree as activated content. I've been there too. But imagine this - you've got say 10 sites each with approximately 500 pages and each page on average consisting of 15 resources. That gives you total of about ...

Date: March, 26 2010
Url: http://www.java.net/blog/rah003/archive/2010/03/24/flush-cache

Others News