html-template-users

[htmltmpl] Speed

[Octavian R. <ora...@fc...>]

Hi,

I have some questions that I couldn't find an answer for:

Which way of "inserting" vars in HTML::Template is the fastest?
(or it doesn't make any difference?)

$ht->param(var1 => $var1,
var2 => $var2,
var3 => $var3);

or

$ht->param(var1 => $var1);
$ht->param(var2 => $var2);
$ht->param(var3 => $var3);

or another one?

-

Is the speed of H::T affected if using the following options?
(incresed or decreased?)

loop_context_vars => 1,
die_on_bad_params => 0,
global_vars => 1,
-

Is there a better way of defining the $ht object than defining it for every
template needs to be parsed?
For example, defining a general object in a separate package, then using it,
giving it the filename of the template, and possible other options...? Could
the speed be bigger?

I could try to test all these things myself, but if not using them in a real
work environment the results might not be relevant, so that's why I am
asking you.

Thank you very much.

Teddy



Teddy

Re: [htmltmpl] Speed

[Paul B. <pb...@wh...>]

On Dec 2, 2005, at 12:09 PM, Octavian Rasnita wrote:

> Hi,
>
> I have some questions that I couldn't find an answer for:
>
> Which way of "inserting" vars in HTML::Template is the fastest?
> (or it doesn't make any difference?)
>
> *snip*

Someone can correct me if I'm wrong, but based on the usual perl speed 
generalizations, doing...

   $ht->param(foo => 1);
   $ht->param(bar => 2);
   $ht->param(baz => 3);

...will be slower than doing...

   $ht->param(foo => 1, bar => 2, baz => 3);

...because doing three method calls is more expansive than doing one 
and passing more data. But doing...

   $ht->param({ foo => 1, bar => 2, baz => 3 });

...should be even faster because it is more efficient to pass a single 
hashref in a method call than it is to pass a large list of arguments. 
I have not benchmarked these and have not looked at the under-lying 
code of the param method to be sure, but based on what I know about 
Perl and the speed of method calls and passing arguments, these are my 
assumptions.

> Is the speed of H::T affected if using the following options?

And I'm not sure about die_on_bad_params, but I do believe 
loop_context_vars and global_vars does add a performance hit because 
the engine then has to generate or handle more vars inside a loop than 
if they were turned off.


> Is there a better way of defining the $ht object than defining it for 
> every
> template needs to be parsed?

I don't have an answer for that.

-- 
Paul Baker

"The day Microsoft makes something that doesn't suck is probably the 
day they start making vacuum cleaners."
           -- Ernst Jan Plugge

GPG Key: http://homepage.mac.com/pauljbaker/public.asc

Re: [htmltmpl] Speed

[Octavian R. <ora...@fc...>]

From: "Paul Baker" <pb...@wh...>
>
> > Is the speed of H::T affected if using the following options?
>
> And I'm not sure about die_on_bad_params, but I do believe
> loop_context_vars and global_vars does add a performance hit because
> the engine then has to generate or handle more vars inside a loop than
> if they were turned off.
>
>

Ok, thank you. Do you know if there is another way of using some vars in a
TMPL_LOOP than using global vars?
Can I "localize" them somehow?

I usually need to use some "external" vars which are not keys on the
hashrefs in the arrayref that defines the loops, but because of speed
penalties I don't want to use global_vars => 1.

Are there any tips and tricks on how can I do this without using
global_vars?

Thank you.

Teddy