quote from the mailing list:
By default, the benchmark tests creating a new
Template object every time, which no one should ever do.
is the TT object guaranteed to stay in shared memory? if not, it might use a lot of memory for every single apache process. (i have a little memory benchmark in the HTC package, but it needs a clean-up, so at the moment I probably don't get correct results on how much memory a TT object consumes.)
HTC is designed to stay in shared memory (*), and it does the object caching itself, so the programmer doesn't need to take care of caching the template objects. this would be nice
for TT, too.
update: ok, now I get your point - the TT object is not file specific. i'll update my testsuite, thanks =)
* except when using options formatter, filter or dumper - options which cannot be converted into written perl code at the moment