Hi,
Thanks for the response.
I have been using the 'preload' setting since it is the default, I did
try the 'lazy' setting as you proposed and surely it loaded real fast
both during startup and when using the 'reload' command in Maverick.
I still have some questions about the caching procedure though.
Is there any difference between how Maverick loads the config file when
starting the servlet container and when using the 'reload' command?
The reason I'm asking is that I've been monitoring the servlet container
during startup and reload and here is what I found:
In these figures I'm using Tomcat 4.1.12.
* Starting servlet container using 'preload' setting in Maverick:
Maverick loads all commands and views in about 50 seconds.
Servlet container is using about 77MB of memory.
* Performing a reload using the Maverick command without using the
application (reload directly after startup).
Maverick loads all commands and views in about 83 seconds.
Servlet container is now using about 103MB of memory.
If I use the application clicking around aimlessly directly after
startup, the servlet container increases it's memory usage for every
unique command executed. Sometimes when trying a reload after using the
application for a while, it times out due to out-of-memory error.
I'm not really sure what these numbers actually say but if I focus on
why it takes so long to do a reload the problem is a probably a memory
issue on my computer, I don't think I have enough memory (256MB and
other programs running) so I think it starts to swap.
Interesting though is that the reload consumes memory, I thought that
when using 'preload' the xsl templates would already be cached.
Maybe I've misunderstood something here?
It works great if I don't do a reload, which I probably won't do on a
production-server, which by the way will have more memory also.
regards,
/Magnus
Jim wrote:
> Yes maverick supports this. Actually has 3 settings for xsl templates
> caching:
>
> "preload ", "lazy", and "disabled"
>
> disabled disables template caching and is very helpful on a dev
> server, but should never be used on a production server. On a
> production server, use "preload" or "lazy". preload will load all the
> templates at startup or when the reload command is issued. This is the
> default setting. lazy will load the templates when they are first
> called. This will make startup and reload much faster, but will cause
> pages to load slower the first time they are accessed as the template
> will have to be loaded.
>
> Magnus, I suspect that you may want to experiment with the lazy
> setting to fix your slow reload problem. Use it like so:
>
> <transform-factory type="xslt"
> provider="org.infohazard.maverick.transform.XSLTransformFactory">
> <template-caching value="lazy"/>
> </transform-factory>
--
________________________
Magnus Rosenquist
Zyneo
http://www.zyneo.com
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
[INVALID FOOTER]
