My web application was using 90% of CPU (w3wp was showing 90), and hence inorder to solve that problem we have identified few ways and one among them is to create a separate Application Pool for the my web Application and set the option Recycle Worker Process at the following times[(night)] under Recycling tab.

Can any one please suggest whether setting the recycle option is harmless or it is harmful to set this option.

Along with that can any one share KB article to support the answer as I need to provide an article from Microsoft to support the answer.

Regards,

Pavani.S.L

 Hello,

Good question, which you could ask in http://forums.iis.net , the same login as here.

Regards

 Hi,

Personally, set a suitable time for Application Pool is helpful. Application Pool recycles is used to release memory, get rid of potentially crash and improve performance. But when Application Pool recycles, ASP.NET state will be lost.

The good recycle time is that we don't get the crash during Application Pool is running and user state is lost least. To get this balance time, we might need to do more test or check logs. ASP.NET Health Monitor is good tool.

In your case, you can configure it basing on your requirement, such as memory pressure.

For more information about Configuring Worker Processes for Recycling, see http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/f11b8294-cc42-4e9c-8482-6257bf3b80f2.mspx?mfr=true

I look forward to receiving your test results.