Creating an app pool a month to limit the scope of issues
Posted
by user39550
on Server Fault
See other posts from Server Fault
or by user39550
Published on 2010-04-02T14:18:38Z
Indexed on
2010/04/02
14:23 UTC
Read the original article
Hit count: 490
app
|application-pools
I have about 360 sites running on a single app pool. Now I know we have a coding issue with one of those sites, were we have accidentally coded a memory leak. So what happens is the site runs, the memory leak starts and soon the app pool runs out of memory. Then slowly but surely, the rest of the 360 sites start going down like a domino affect. I understand that the root of the problem is some bad coding, which we'll fix, but instead of bringing down said 360 sites, I was thinking, we could create a new app-pool monthly that every site we create would go into that months app pool. First, that limit the scope of the issues to 5 - 20 sites and second if one site started having issues we wouldn't be bringing down all 360 sites.
Is there any issues to this thinking, possible ramifications? Thanks in Advance! Jeremiah
© Server Fault or respective owner