Restarting application pools
-
Hi, I have some questions regarding application pools and the different types of web sites in asp.net. As far as I understand, an application pool will reset after 20 min idle time by default. But once that occur, we are experiencing a huge perf hit when accessing the first page in the site. I get the impression that the site will start recompiling again. The project type is the vs.net 2005 "web Site" project that does not compile the codebehind into a static dll in the bin folder I can't recall ever having this problem when I have worked with the older "web Project" projects. So is the problems I'm experiencing related to the fact that the codebehind is not precompiled and that the reset of the app pool throws away the compilation result of the previous worker processes? or is the perf hit simply related to alot of overhead in starting up the worker processes? Any ideas? Will the problems go away if we change the project into a "web project" with precompiled codebehinds. Or is the only solution to only allow the app pools to reset once every night or so?
-
Hi, I have some questions regarding application pools and the different types of web sites in asp.net. As far as I understand, an application pool will reset after 20 min idle time by default. But once that occur, we are experiencing a huge perf hit when accessing the first page in the site. I get the impression that the site will start recompiling again. The project type is the vs.net 2005 "web Site" project that does not compile the codebehind into a static dll in the bin folder I can't recall ever having this problem when I have worked with the older "web Project" projects. So is the problems I'm experiencing related to the fact that the codebehind is not precompiled and that the reset of the app pool throws away the compilation result of the previous worker processes? or is the perf hit simply related to alot of overhead in starting up the worker processes? Any ideas? Will the problems go away if we change the project into a "web project" with precompiled codebehinds. Or is the only solution to only allow the app pools to reset once every night or so?
A general answer to your post would be, Yes. Precompiling the page will save you a lot of startup time. I would untick the idle timeout, and instead recycle the processes at night when noone is using the homepage (if that's an option that is) No recycling at all would be a bad advice though. The default IIS setting seems to have the purpose to make it possible for even badly programmed pages with memoryleaks (AKA Crystal Reports) to work fairly well
-
A general answer to your post would be, Yes. Precompiling the page will save you a lot of startup time. I would untick the idle timeout, and instead recycle the processes at night when noone is using the homepage (if that's an option that is) No recycling at all would be a bad advice though. The default IIS setting seems to have the purpose to make it possible for even badly programmed pages with memoryleaks (AKA Crystal Reports) to work fairly well
Thanks, Precompiling took care of the problems. I do think that 20 min idle is way too drastic for the reset, but that is not up to me to decide here.
-
Thanks, Precompiling took care of the problems. I do think that 20 min idle is way too drastic for the reset, but that is not up to me to decide here.
Just keep in mind that the app-pool idle timeout has to be the same or longer than the asp.net session timeout