In a low traffic site, yes. In a very high traffic site, with lots of objects, the mkdir's kill you. After a "while," most of the directories will be created. However, bringing up a "fresh" server behind a very busy site is bad in this case. Perhaps, what mod_disk_cache does now is best and the pre-make directories script should be "contrib."
*nod*
Also, any thought son how to handle Vary? I have a way to do it in our cache, but it seriously violates the RFC's. There is a config directive that defines what aspects of the request are used to generate the MD5 (virtual host, url, args, header values, environment values, etc.) and thats it. Only useful when you know a lot about the content being served, which is the case for a reverse proxy usually.
After I know that mod_cache isn't doing anything stupid or damaging performance-wise, I'd like to start being more aggressive about what we can cache. From my perspective, these patches I've posted (and started to commit) are just the beginning of trying to get mod_cache on more solid ground both performance and RFC-wise. And, that needs to happen before mod_cache can even get out of experimental... -- justin
