This is a possible issue for us too. We'll be doing all the standard things to make the processing as efficient as possible, but some of our transforms will take 4-5 seconds (with Xalan) and it would be impractical to pre-transform all of the possible combinations.
What would be nice would be a cache-warming transformer. Something that could be part of a pipeline that would kick off other pipelines, in another process or in the background, to cache those outputs on the assumption the user is likely to be going there next. It would be nice if it could handle URIs and URIs with wildcards or sets of possible values. Thoughts? >>> [EMAIL PROTECTED] 06/25/02 10:51AM >>> First have a look at http://xml.apache.org/cocoon/performancetips.html Then, look also at the run.sh|bat command line to run cocoon without web interface. That way, you can easily design cronjobs to get it running at scheduled times over nights Regards, Denis ----- Original Message ----- From: David Vos To: [EMAIL PROTECTED] Sent: Tuesday, June 25, 2002 5:40 PM Subject: Warming the cache. As we are moving more of our web site over to cocoon, we are starting to run into some speed issues. There are several ways we could speed things up from a processing side (split some of our xml files up to drastically speed up parsing), however there are some things that may take at least 10 minutes to complete (dynamically generating microsoft reader format for files larger than a megabyte). Therefore, it would be nice to have cocoon generating all of these overnight so that as they are being accessed, response time will be much quicker. What might be the best way to do this (besides a script calling wget http://localhost/... all night?). How large can the cocoon cache grow? David --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
