On Nov 23, 2008, at 14:55 , Nathan Bubna wrote:
Hmm. It's doesn't seem quite that straightforward to me. Caching isn't always a parse-all-up-front situation, there are modification check intervals, and most of all, there are things that can heavily use evaluate(...) (RenderTool, #evaluate, etc) instead of getTemplate(...).
Good point, even though I think these things should be cached when performance is important.
This is something i put in the "if it's not broken, don't fix it" category. If you know that you don't need a parser pool, then by all means, set it to 1. That's why it is configurable. But i would worry about changing that on people without some real numbers and case studies. Until then, no one has complained about the extra parsers kicking around to my knowledge.
Agreed, I don't think it should be changed, I just bring up the pool size of 1 for exemplification. My general point is that the insinuation that the pool size is something that needs to be tuned for a high traffic site is maybe confusing. However, I'm not advocating any changes, I'm just talking out load :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
