Hi, I am a member of a small group developing a web site using Tomcat and Cocoon and we are having some problems with the efficiency of the site. We were wondering if all of the lib jar files for Cocoon were loaded into memory, by default, on start up or whether they are loaded into memeory as and when required? Any thoughts people?
In general, no I think that Classloaders load on demand.
However, if you are using a "kitchen sink" build of cocoon with lots of blocks that you don't use and lots of poolable sitemap components (generators, transformers, serializers) that you don't use but have pool-min above 0 you are going to have lots of them loaded because of the avalon lifecycle. This will translate to memory use you don't need.
Also check your logging level which drags down performance and all the other recomendations on the "performance tips" page in the docs.
Finally you need to evaluate whether your own application design is the problem. Possible culprits:
- doing lots of(heavy) xsl transforms in a pipeline
- creating dynamic xsp
- lots of uncacheable pipelines with heavy processing
- big xml files or sources
- reading from remote sources (using http:// protocol in src in your pipelines)
- xml files with dtd references if you don't use the entity catalog (each dtd will be looked up across the network during processing).
Try using the profiling pipeline for some testing - it could help turn up some culprits.
HTH, Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
