Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

About IIS application pools

Posted on 2014-12-17
2
Medium Priority
?
122 Views
Last Modified: 2014-12-17
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!
0
Comment
Question by:gdemaria
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 29

Accepted Solution

by:
Dan McFadden earned 2000 total points
ID: 40505448
I recommend that you do not share AppPools.  If you do, any 1 web application in a shared AppPool can crash the entire AppPool and all web apps using the shared pool.

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
0
 
LVL 39

Author Closing Comment

by:gdemaria
ID: 40505461
I'm convinced - thanks!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The reason that corporations and businesses use Windows servers is because it supports custom modifications to adapt to the business and what it needs. Most individual users won’t need such powerful options. Here I’ll explain how you can enable Wind…
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question