Dean,

Typically you are ok with the standard ASP.NET worker process settings which is an application pool restart after 20 minutes of inactivity.

An application pool re-cycle will cause your DNN instalation to take a bit longer to respond to the next request as DNN must be compiled before the request is processed.

What timeframe are you looking at needing a recycle for your Crystal Reports?  I have worked with clients that would recycle forcefully every night and it worked for them as they didn't have much load at night.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Your users don't normally get logged out as it starts a new process before finishing the old one.

You need to set recycling directly on the server using IIS manager. If you look in the IIS help (click the help button when you're looking at the app pool properties) there is information on the various methods of "Recycling Worker Processes". Pick one and tick the boxes.

I've experimented and found that the memory usage triggers don't seem to work accurately - I can tell it to recycle a pool at 500Mb but it just keeps recycling at 200Mb or so. In the end I've gone with a regular fixed 3 hour recycle, though I'd really prefer to use the memory method.

Has anyone got tips on using memory usage triggers for reycling?

Rob