Hi Group,<o:p></o:p>
<o:p></o:p>
There has been a lot of times when we feel that our application is slowing down or the ASP.Net worker process is not working as its best. Although ASP.NET does recycle its process after certain number of requests or memory Limit but there are times when you feel that you could control these parameters and explicitly restart the worker process.<o:p></o:p>
<o:p></o:p>
It is possible to restart the worker process explicitly after a certain number of requests. <o:p></o:p>
In Machine.config under <configuration> <system.web><procesmodel> we have an attribute called requestLimit.<o:p></o:p>
<o:p></o:p>
Set this request Limit to the number of requests after you want to recycle your worker process. It can be set to Infinite or any particular number. The default setting is 5000.<o:p></o:p>
<o:p></o:p>
Suppose if we set to it say 10 then you will notice that after every 10 requests aspnet_wp process will be recycled. You can note the process id's to feel the change.<o:p></o:p>
<o:p></o:p>
Second reason coz of which we may want our process to be recycled is because of high consumption of memory.
<o:p></o:p>
In Machine.config under <configuration> <system.web><procesmodel> we have an attribute called memoryLimit. Set the threshold to the amount you want. The default is 60 i.e. 60%. The moment this threshold is reached aspnet_wp will be recycled.<o:p></o:p>
<o:p></o:p>
Before we make any changes to the machine.config we must remember that these changes are going to affect all the applications on that machine coz we are these changes at the core level. Hence after making these changes we should bench mark all our <o:p></o:p>
applications.<o:p></o:p>
<o:p> -- Please post your queries and comments for my articles in the user group for the benefit of all. I hope this step from my end is helpful to all of us. You can find all articles written by me at my personal blog http://spaces.msn.com/members/nasha.
Regards,
Namratha (Nasha)
[EMAIL PROTECTED]
</o:p> 
