Geek Answers Handbook

What are the advantages and / or disadvantages of running each website in your own AppPool?

We have several sites that have some memory problems and quite often crash and delete many other sites from them. Therefore, I plan to at least put nasty sites into my own AppPools. I just wanted to make sure this was a safe step or something I should know about splitting AppPools.

+4
source share
3 answers

Each application pool has a memory that contains a couple of megabytes, if the problem is due to lack of shared memory. This may not help.

Having said that, we run all of our websites in our own application pools by default, but we usually have a maximum of one server, so I have no experience with a large number of application pools at once.

We also see that the benefits of being able to process one application pool without affecting other sites are a big advantage.

Finally, as well as isolation (as Guff mentions), you can configure the settings of each application pool to limit memory usage, etc., as well as identifiers and permissions. (We will use different websites with different accounts that would only have permissions for their own databases)

You can also find out about this by Server Fault error: https://serverfault.com/questions/2106/why-add-additional-application-pools-in-iis

+4
source

Advantage:

  • Separate credentials for each application pool / website
  • Better insulation, recycling, etc.
  • Separate configuration (timeout, memory, etc.)

Inconvenience:

  • Memory usage is increasing (not so much a problem with 64-bit these days)

There is usually no shortage. If you have a huge number of sites on one web server, whether it is separate application pools or not, this is a small problem.

+3
source

The advantage is that you isolate the site in your own process.

The disadvantage is that more processes are running on the server.

So, if you do this in just a few sites, there should be no problem.

+2
source

More articles:


All Articles