|
Hi,
I am new to Template::Toolkit, and I am hoping to integrate it into my company’s high-traffic e-commerce site (as part of a Catalyst application running on mod_perl 1.29). I have written a small sample app in our development environment to see how Catalyst performs. I am in the process of examining the running app via the perl-status utility in mod_perl, and I am finding that the most memory intensive functions are part of the Template::Toolkit suite.
Here are some snippets from various memory views in perl-status.
Template::Timer::process: 183780 Template::Service::process: 194319 Template::Context::process: 196594
Template::Timer looks like a debugging mechanism, so I’m guessing that it can be turned off when the production application is deployed. However, the other two process() functions are large. On drilling down into them via perl-status, I found that this is because they contain large entries in something called the PADLIST summary (not sure exactly what this means). For instance, here is a reporting of what appears to be a large scalar value that is “stuck” in the process.
19: $output [PV 89642 bytes]
|
- [Templates] Template::Toolkit efficiency Simon Miner
- Re: [Templates] Template::Toolkit efficiency Perrin Harkins
- Re: [Templates] Template::Toolkit efficiency Todd W
- Re: [Templates] Template::Toolkit efficien... Randal L. Schwartz
