On Thu, 2005-08-18 at 12:53 -0400, Simon Miner wrote: > Template::Timer looks like a debugging mechanism, so I’m guessing that > it can be turned off when the production application is deployed.
Yes, Catalyst just adds that in for you when you are in debug mode. > Upon investigating the Template::Context::process code, I found that > $output contains the interpolated version of the template, and is > returned to the caller. Right, this is how the caching works. You could disable caching or reduce the size of the cache if you are willing to trade some speed for memory. > - Will the size of the process() methods continue to grow as the > number of calls to them increases? The memory used by TT will grow when you compile new templates. It may also grow if you pass in larger data resulting in a larger output string. > - I noticed that the process() method returns $output as a scalar > value, as opposed to as a scalar reference. There are all kind of options for controlling this. Read the docs for the Template module. > - What are the best ways to make the Template::Toolkit as efficient as > possible? Use PROCESS instead of INCLUDE. - Perrin _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
