Be seen. Boost your question’s priority for more expert views and faster solutions
About IIS application pools
I am new to IIS 8 (running on windows 2012 R2 an Amazon EC2 server).
I am creating a bunch of websites to migrate to this new server. Each time a configure a website, IIS creates a new application pool for me using the name of the website.
Should I allow websites to share the same application pool? It seems to be a setting that allows me to share settings or something, but I am not sure which settings and what strategy I would use to decide to share or not to share.
I do have some websites that use HTTPS, I do have some that have a lot of visitors and some that have few visitors, not sure what else..
Thanks for any help!
I am creating a bunch of websites to migrate to this new server. Each time a configure a website, IIS creates a new application pool for me using the name of the website.
Should I allow websites to share the same application pool? It seems to be a setting that allows me to share settings or something, but I am not sure which settings and what strategy I would use to decide to share or not to share.
I do have some websites that use HTTPS, I do have some that have a lot of visitors and some that have few visitors, not sure what else..
Thanks for any help!
Asked:
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
If multiple websites use 1 AppPool, the only "shared" settings are that of the AppPool. There are no specific website configurations shared among websites using the same pool.
I recommend 1 AppPool per website. This provides isolation from crashes. If 1 website crashes, it only takes itself and its AppPool with it.
Having AppPools with the same name as the associated website helps in management of the various sites and associated pools.
Its best to isolate (1 website per pool) websites that are based on PHP, ASP.NET, etc. This way issues only effect the site itself. You could, if you wanted to, share AppPools with static websites. Sites with no dynamically generated content that server only HTML with minimal JavaScript. There is less of a chance that a static HTML site will crash a pool just from a developer doing something odd in HTML.
Decent reference link: http://blogs.msdn.com/b/cenkiscan/archive/2012/06/20/iis-best-practices.aspx
Dan