file: $CPAN/authors/id/P/PE/PETDANCE/Template-Timer-0.01.tar.gz
size: 2489 bytes
md5: a77568ba820f26d81be05fef4f2d02e4
I bundled up the functionality that Gavin posted and Randal modified.
Now, people in my situation ("Surely there must be a profiler
somewhere!") have a tool they can easily find.
Template::Timer provides inline timings of the template processing
througout your code. It's an overridden version of Template::Context
that wraps the process() and include() methods.
Using Template::Timer is simple.
my %config = ( # Whatever your config is
INCLUDE_PATH => "/my/template/path",
COMPILE_EXT => ".ttc",
COMPILE_DIR => "/tmp/tt",
);
if ( $development_mode ) {
$config{ CONTEXT } = Template::Timer->new( %config );
}
my $template = Template->new( \%config );
Now when you process templates, HTML comments will get embedded in your
output, which you can easily grep for.
<!-- TIMER START: process mainmenu/mainmenu.ttml -->
<!-- TIMER START: include mainmenu/cssindex.tt -->
<!-- TIMER START: process mainmenu/cssindex.tt -->
<!-- TIMER END: process mainmenu/cssindex.tt (0.017279 seconds) -->
<!-- TIMER END: include mainmenu/cssindex.tt (0.017401 seconds) -->
....
<!-- TIMER END: process mainmenu/footer.tt (0.003016 seconds) -->
<!-- TIMER END: include mainmenu/footer.tt (0.003104 seconds) -->
<!-- TIMER END: process mainmenu/mainmenu.ttml (0.400409 seconds) -->
Note that since INCLUDE is a wrapper around PROCESS, calls to INCLUDEs
will be doubled up, and slightly longer than the PROCESS call.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
_______________________________________________
templates mailing list
[EMAIL PROTECTED]
http://lists.template-toolkit.org/mailman/listinfo/templates
