From: Dan Ackroyd [mailto:dan...@basereality.com] > What context are these filesystem hits in, is it class autoloading > by any chance?
Not really. Drupal is looking for 'sites.php' in the root of the web site, and then probing lower down and finding it. It's also looking for 'settings.php' in the root of the web site, and 'includes\database\mysql\select.inc' and 'themese\<theme_name>\favicon.ico'. Now, admittedly, this may just be a Drupal site owner with a mis-configured site/app install, but since the site continues to function with good content (just slowly), it's not terribly discoverable that the site owner could just tweak a few things and go faster... > > Does the PHP stat cache include negative cache entries? If not, why not? > > For example, a browser caching a page that returns a 200 response is fine, > as it's caching some information that was acceptable. A browser caching > a 50x error page would just be caching useless information. Agreed that HTTP 5xx errors are never a good thing to cache. However, some servers have seen improvement by caching 404s. See: http://highscalability.com/blog/2010/3/26/strategy-caching-404s-saved-the-onion-66-on-server-time.html It's in this spirit that I was considering the option of negative caching for file_exists, is_file, is_dir, etc.. Thx! --E.