William A. Rowe, Jr. wrote: [...]
>>>The reason I'm asking is that in CNET's case (and probably other corporate >>>web-sites) >>>most of these things would be set only once, and all the merges are just a >>>waste of CPU. >>> > >Not anymore ;) That is, we might have a few merges, but they are an order >of magnitude faster on subrequests and redirects. > In the last set of profile data that I checked (based on tests of a Sept 27th CVS snapshot), the mod_mime dir_merge was still one of the most expensive operations in the httpd: 3.6% of total CPU time, and 14% of non-syscall CPU time, for a test case using mod_include with two subrequests per request. If directory_walk and location_walk are in a stable state, I can revisit the static caching of merged configs to fix this. (But if you're still working on changes to these functions, I'll wait.) Alternatively, Ian's proposal will solve the performance problem more easily, if users can live without directory-specific overrides to the MIME type mappings. --Brian
