Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Pros and cons of having dedicated application pools over keeping web applications in one default app pool

What are pros and cons of having dedicated application pools over keeping web applications in one default app pool?

like image 784
GrZeCh Avatar asked Oct 21 '08 20:10

GrZeCh


People also ask

Can one web application have multiple application pool?

Yes, create "Applications" out of each sub folder. Than the application can have a separate application pool, the same will work for Virtual Directories.

What is the benefit of application pools?

Application pools allow you to isolate your applications from one another, even if they are running on the same server. This way, if there is an error in one app, it won't take down other applications. Additionally, applications pools allow you to separate different apps which require different levels of security.

What is an application pool and why might you use different application pools for different sites?

Application pools can contain one or more worker processes. Each worker process represents work being done for a Web site, Web application, or Web service. You can create a Web garden by enabling multiple worker processes to run in a single application pool. In IIS 7 and later, each application pool uses one of two .


2 Answers

Pros:

  • Applications are isolated from each other, unless IIS goes with it, an app pool locking will only take out applications in that pool
  • Ability to run applications under different ASP.NET runtimes, one pool for 1.1 another for 2.0 if needed
  • Ability to have different app pool settings for more or less critical applications. For example a corporate website in ASP.NET might want to have the shut down after __ minutes of inactivity bumped up, to prevent unloading because response is critical. Other sites might not need it.
  • Can secure pools from each other in regards to file access, great for third party, or untrusted applications as they can run under a very restrictive user account.

Cons:

  • Each application pool has its own bank of memory and its own process, therefore CAN use more resources
  • Some find it hard to debug the application as you have multiple processes
like image 174
Mitchel Sellers Avatar answered Sep 28 '22 01:09

Mitchel Sellers


The primary reason for combining sites in app pools is to conserve memory. There's a large memory overhead in running several w3wp.exe processes. If you have no specific reason for splitting them up, it's better to keep them together.

like image 31
Mark S. Rasmussen Avatar answered Sep 28 '22 00:09

Mark S. Rasmussen