Andy Lester wrote:
In my experience (admittedly warped experience) the number one culprit for heavy usage on a TT site is DB access. More than once I've seen people doing a heavyweight connect/login to their DB for every page or request, rather than holding a pool of open DB handles.We're doing this, and it's working marvelously. Now, what else can I do to speed things up? Heck, I'd settle for rudimentary profiling to see which of the templates is dragging our server down the most.
We've left CACHE_SIZE at its default setting to let everything get cached. There are only ~125 files on the entire site, including subcomponents, so I doubt the cache is getting bogged down?
Our web server is pinned on all both CPUs, so anything we can do to reduce the load will be a help. I'm not seeing anything in the Badger or the docs that is a help.
Suggestions?
Number two has to be the bad habit of pulling in entire DBs and then filtering/joining the rows with perl or TT before display rather doing the heavy work in SQL. Hopefully you aren't doing that but I've seen it too many times to not ask about it. :-/
Profiling is an obvious next step. I'd do that next.
--mark
_______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
