On Wed, 24 Nov 2004 14:44:49 -0500, Jesse Sheidlower wrote
> I was discussing profiling with Perrin recently, and he mentioned
> template compilation is a potential area for big improvement. When
> pressed, he delivered me the attached patch, which I share with his
> permission. This is for Maypole::View::TT, and is very simple, using
> Template::Provider.
>
> I've tested this out on two Maypole apps, and it realizes an
> improvement of 250-500% on requests/second output on various pages.
> That by the way is the overall output, not a profiled improvement
> of the template-processing stage alone.
How does that compare to using the COMPILE_* options in Template.pm? Am I
right in assuming that the COMPILE_* options will store the compiled templates
on disk while Perrin's patch allows you to cache the templates in memory?
If that's the case, I think we should have both options so users of
Maypole::CGI can see some improvements in templating performance too.
--simonflk
_______________________________________________
maypole-dev mailing list
maypole-dev at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole-dev
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT