Application Pools for Multiple Websites

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

Thank you!
luizmottaAsked:
Who is Participating?
 
Tray896Connect With a Mentor Commented:
Yes, I would suggest that you use one app pool for each website.  I'm curious how you've been able to run them all in one app pool this long?  You can't run multiple versions of .net within the same worker process, so having such a huge number of apps sharing a pool is bound to cause problems.

I always create a new app pool for each site and this way I can isolate any problems that come up.  
0
 
luizmottaAuthor Commented:
Thank you for your feedback. I'd say the web sites I'm hosting have a relatively low about traffic, so that is why only now I've been running into problems. Also, the majority of the sites run off the same code (we offer a few different web templates) and I am in control of the code.

Do you think I should anticipate any issues if I were to create 200+ app pools for these websites?

Thanks!
0
All Courses

From novice to tech pro — start learning today.