I am creating new web applications and creating a new app pool each time. Is there a downside to doing this?


Application Pools are fairly expensive. I will often advocate/build farms with the minimum number of accounts possible (for those covering App Pools, that would be a Farm Admin, Service App, and Web App account).

With .NET, there is minimal memory sharing between processes, and the SharePoint binaries consume quite a bit of memory without any end user activity.

  • OK - I'm creating the app pools on the Development server though. So will this still be an issue? – jahlive Jan 27 '16 at 16:14
  • That would be your decision to make. There's nothing stating that it is wrong/will cause an issue, but just know that there is an increased memory usage. If you have 32GB RAM dev server and you create 5 Web App Pools but you're the only user, no you're not going to run into memory issues (most likely). – Trevor Seward Jan 27 '16 at 16:17

The downside is: you can hit the recommended limit of 10 app pools: see https://technet.microsoft.com/en-us/library/cc262787.aspx#WebserverAppServer.
Also note the limit of Web applications (20).

  • Is there any reasons to why there is a recommended limit? Please elaborate your answer. – Christoffer Jan 27 '16 at 15:03
  • 1
    Unfortunately, the article I mentioned is the best resource we can have on this subject. As they suggest, it's all a matter of performances (remember accounts, check health, monitor services...). Plus, to be honest, a matter of maintenance. Also, dont forget that you also have the 20 Web apps limit... – Evariste Jan 27 '16 at 15:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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