|
Thursday 18 October 2007 3:25:27 am
Regardless all this after 2 hours the view cache is set invalid and again 5 seconds to build it. Can someone tell me what it's going on? Can I set this 2 hours time to 24 hours (I have a crawler that feeds the cache at night) ?
Viewcache is normally not invalidated by time, so this is probably your cache blocks invalidating (they invalidate every 2 hour unless you specify something else).
To invalidate view cache every 2 hour you would have something like this in your node template:
{set-block scope=root variable=cache_ttl}7200{/set-block}
So you should look into tweaking your cache blocks, remember to not have to many of them, evaluate if you can use subtree_expiry or even ignore_content_expiry to reduce cache invalidation as much as possible. And specify expiry time so that they survive more then 2 hours.
As for performance when stuff is uncached, this is hard to help you with without looking at the code. But rule of thumb is:
* Template code is slow, 10 lines of template code could result in 1000 lines of compiled php code. So rethink any site logic that is controlled by templates and take advantage of the permission / override / content class system if you can.
If not, rewrite any heavy logic to a custom template operator. The php api of eZ publish is far richer then the stuff you have access to in templates, so it is likely that you can do things more efficiently there as well. * Pay close attention to how many database calls that are made during a uncached request. Any page with over 200 sql calls pr request should be looked at. * Consider upgrading to eZ Publish 4.0 as soon as it's gold, it will normally give you a performance improvement from 50-200% over what you have, and in some edge case even more.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
