Application Pools for Multiple Websites
Posted on 2009-07-16
My server is currently hosting over 200 websites. The websites only get moderate amounts of traffic so performance hasn't been a big issue, but there has been some stability problems at times. Up until recently I have been using only one application pool for all the sites. As the number of sites grew, all the websites would start crashing. That's when I noticed the process for the application pool was getting to be around 500 megs. Once I recycled the pool, the sites were working again. At this point I started going through the code to take care of possible memory leaks, and I split off about 50 of the web sites into another application pool. So far, no problems.
My question is, would I be better off using one application pool for each website?
Here's a little info about the server: Server 2003, IIS 6.0