On Jul 3, 2005, at 11:43 AM, James Moore wrote:
While it makes sense to point out to inexperienced developers that
premature
optimization is usually a bad idea,
Premature optimization is always a bad idea, by definition.
In particular, I'd be inclined to disagree with your asssement of the
impact
of all those stat calls in a large-scale NFS environment. Anything
you can
do to reduce gratuitous NFS traffic I'd think would be more than a good
idea. Plus I'd suspect that there would be side effects; for example,
how
do extra stat calls hurt caching of things that you really do care
about?
"I'd think", "I'd suspect": Pointing at the lack of measurement.
If the optimization isn't measured, how do you even know you've
improved things? And how much? Is it worth your while?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
