On Sun, Sep 09, 2007 at 09:20:53PM +0200, Jeremiah Foster wrote: > >I see. When you mentioned memcached that made me think you wanted to > >share across servers. I don't see memcached helping here, but I might > >be wrong. It's not like you can use memcached as extra memory for > >your process. > > > > Though I do not claim to be an expert in this area, memcached is in > fact a "giant hash table distributed across machines" and does in > fact allow for significant speed increase. Caveat emptor.
I'm no expert on memcached either, but my point was that using memcached for caching the parsed templates would not avoid the need to have the templates in memory in the process. What might be interesting is to use memcached for the LOOKUP store. Moving that cache out of the process space might be helpful. Or as a cache between the LOOKUP store and compiling of the templates, since it's handy to keep common templates in memory. Might be useful for Peter to alter Provider to see how much space is actually used by the LOOKUP hash once loaded with templates. A simple test might be to just disable it and see how much savings there is by setting CACHE_SIZE = 0, IIRC. -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
