Iis – Do unused application pools in IIS affect performance

application-poolsiisperformanceworker-process

Due to a major update in our architecture, we now have a few unused application pools under IIS (there are no web sites mapped to them).

I understand how it can a good idea to remove them just to improve readibility, but my question is more about performance implications: Does having these unused application pools matter in term of memory, CPU, IIS request processing speed, or any other performance metric?

From what I can see, an application pool with no web sites does not create a worker process, so I suspect there's no difference in performance, but I want to be sure I'm not missing something.

Best Answer

The only overhead incurred will be the few bytes taken up in applicationHost.config to define the Application Pools and any non-default settings they may have.

If you have a 1000 unused app pools it might improve the time it takes to apply on-the-fly configuration changes to IIS (since there's less XML for the WAS service to parse), but with 5 App Pools I would argue that there is virtually no difference