Hi,

From: "Perrin Harkins" <[EMAIL PROTECTED]>

>
> I suspect you had one of the following problems:
>
> - Incorrectly configured template caching

I don't know too much about caching, but I have just configured TT to create
cached templates, so I have used cache.

> - Heavy use of method calls in your template

No, I haven't used any method calls and no modules calling directly from TT.
I have used only FOREACH loops, variable replacements, IF, ELSE statements,
and the foreach loops were not based on hashes but on arrays already
ordered.
Oh, and I have also used a few URI and HTML filters. (|URI | html)

> - Use of a plugin that fetches data (e.g. DBI queries or a Class::DBI
> object)

No. To be sincere, I have never used those things directly from templates.

> - Programming logic in the template that belongs in the perl code
> instead

I have tested how much time takes to run for each piece of code, and just
before the last $tt->process(), the time was a half of the time needed to
run the entire program, so it doesn't matter how the program was made.

> - Heavy use of INCLUDE rather than PROCESS

I have used only PROCESS in the templates, and not even a single INCLUDE.

TT is a great templating engine but in my opinion is not very good for
beeing used with mod_perl or with programs that need running very fast.

However, it might be important that I have made the tests under Windows...
Maybe under Unix the situation would not be the same.

Teddy


Reply via email to