Smarty

[Tom Sommer]

I'm worried about performance,

I have a function which generates a headline

Called like so

[messju]

if the name is the only dynamic element in your template, that depends on the loop, you can save the return-value of fetch() in your function, then it has to be done only once.

sth like:

[Tom Sommer]

OMG, that lowered the loadtime so much... Thank you, never thought of that

[boots]

edit:

I was wondering why smarty doesn't have a generalized memory cache in front of the persistent output and compile caches. AFAIK, every fetch requires at minimum a disk load of a persistently cached file. I would think that keeping items in a non-persistent cache like that would speed up not only Toms case above, but also speed up all multiple calls to a given template. Further, it could probably be serialized across sessions and eventually (using SRM?) across users.

2c

[messju]

toms case would have been optimized automatically, if caching was enabled: if the templates' output comes from the cache, all included templates' output is also in the cached-file. so there is only one fread() not matter how many {include} statements (even inside loops) you have had in the templates source.

caching parsed php-sourcecode (in our case compiled templates) in shared memory is the domain of php-accelerator. don't bother to build a better solution in php, you cannot win.

caching cached templates' output in shared memory can be a dangerous thing. if you use cache_ids heavily, your shared memory will be full very soon. your application would blow then. or you will have to swap from and to shared memory. thats will be tremendously slower than, letting your operating system do such things. AFAIK linux for example uses all unused memory as disk-cache. so IMHO there's no need to rebuild such a thing at php-level either.

caching the output of a fetch() call has not to be implemented. thats exactly was Smarty's caching does.

caching the output of Smarty's compiler (the compiled templates) cannot be done more efficiently in php as in simply installing phpa.

just my thoughts and 2c

[boots]

I see what your saying. Good points. I guess it would only be useful if there was a shared memory manager and then only for compilation. Since there is no shared memory...