Re: *****SPAM***** [WebMacro-user] Templets & performance

[Keats <ke...@xa...>]

A templet is built (compiled) and cached along with the template in which it
is declared.  The template caching is configurable.  Also, if you save a
reference to a templet you can reuse it indefinitely without rebuilding
(compiling).

Of course the real potential performance hit is probably with expansion
(execution).  I don't know if any benchmarking has been done on this, but in
general it's a good idea to put performance critical stuff into the Java
code rather than the template.  Just beware of "premature optimization" -- 
don't spend time optimizing stuff unless you really see a problem.

Keats

----- Original Message ----- 
From: "Nikhil G. Daddikar" <ng...@ce...>
To: "webmacro" <web...@li...>
Sent: Thursday, February 26, 2004 8:35 AM
Subject: *****SPAM***** [WebMacro-user] Templets & performance


> Should I be concerned about performance issues? I have about 500+
> templets. How do I ensure that these templets are compiled, cached and
> reused?
>
> I instantiate a WM object once and use it across the application. Will
> this in itself mean I avoid the overhead of compiling templets?
>
> Thanks.
>