Thanks!

You mention I'm unfairly benchmarking Template->new... But this is what I'm doing for all modules. So I guess TT uses a different (more scope-oriented) way of caching than the other two modules?

Not that it would matter much in web applications, where frameworks like CGI::Application take care of caching on a higher, persistent level.

I will add HTML::Template::Compiled to my benchmarks too. And perhaps Seamstress – if there's any point benchmarking that module speed-wise – but I'm having a tough time getting it packaged and installed properly on Debian.

So thanks again for your insight, I'm just left wondering why TT seems to use a different sort of caching system than the other modules. I don't think I found any clues to this effect in the CPAN documentation at least...