Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're thinking of updating our server farms to use Shared Configuration, and we're wondering about the performance penalty for doing so.

We're wondering when the applicationHost.config file is read from the filesystem? Every request? Everytime the app pool recycles?

share|improve this question
1… – pk. Sep 1 '11 at 19:26
up vote 1 down vote accepted

When WAS boots, when a change is made, and potentially when an app pool is started.

By default, the configuration is read by WAS (Windows Process Activation Service) whenever either it starts, or a change to Applicationhost.config is detected.

It then cuts that configuration up into individual appPoolName.config files, secured for the individual App Pool Identity that needs to read them (you can find these in inetpub\temp\appPools). This always happens on the local disk, regardless of where the root Apphost.config has been redirected to.

If Config Isolation is turned off, that doesn't happen, and I'm not sure what does :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.