On Sun, Sep 09, 2007 at 08:43:20AM -0700, Bill Moseley wrote: > On Sun, Sep 09, 2007 at 10:52:32AM -0400, Peter Hartzler wrote: > > Going FURTHER out on this limb, it seems like overriding > > Template::Document::write_perl_file() for saves, and > > Template::Provider::_load_compiled() for reads might work. > > What benefit are you expecting from using memcached? Having only one > server parse the templates? The templates only get parsed into Perl > when they change on disk, which it typically not very often.
Bill -- I'm hoping to reduce the overall memory footprint without losing the benefits of caching. (Lazy AND greedy!) Tmpl->Perl parsing overhead is less of an issue for us, for the reason you mention. Our site currently has around 200 templates. What I *think* I'm seeing is memory consumption where each apache instance (child w/ mod_perl) keeps its own cache. The next step from there is the idea of centralized caching. It's entirely possible that other approaches might be better. I'm suspicious of my proposal if for no other reason than the leading '_' in '_load_compiled()' So, your questions, and the testing/verification of any answers, are quite valuable, thanks! Pete. _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
