On 18 Oct 2006, at 13:50, messju mohr wrote:

> If you have caching enabled then smarty stores the rendered output in
> memory in a static var in smarty_core_read_cache_file().

I've got caching turned off - every render is dynamic.

I've tracked this down further. Each set of calls call to $smarty-
>fetch gets progressively slower - starting out at 0.02 sec, rising
to 0.1 after about 5,000 iterations - a factor of 5.

I've stopped the smarty instance from being static, so it gets a new
instance every time, but it's still showing the problem.

It could be one of my smarty plugins that's at fault, but I can't
think why RAM allocated by one would not be released when the smarty
instance is destroyed, or why it should affect the performance of a
completely different instance.

Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk/