While it makes sense to point out to inexperienced developers that premature optimization is usually a bad idea, I suspect it's not particularly useful once you've figured out that you're dealing with someone (or a group of someones) who's put a fair amount of effort into figuring out how their solution scales.
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'll admit to being very curiuos as to why and how they're using NFS in a scaled system, though. In particular, I'd love to hear about dealing with things like failure detection and recovery. Probably outside the scope of this mailing list, though... - James _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
