In the previous version 6.0 and IIS 6 we had all app pools set to recycle every day.
We kept these settings for 6.1 and IIS 7.5, however the first few users that sign on early are complaining of long wait times and unhandled errors.
Should recycling the app pools not be schedule on a regular interval for 6.1?
What is the recommendation?
although custom code (validators, methods, guard conditions, etc) may negate this, we recommend no app pool recycling. app pools should be monitored for memory use, and at a minimum; GSM, GSMView, and NPD should be in their own app pools. After that, the app pool settings as outlined in the 6.1 install/upgrade guide (and reiterated in the 184.108.40.206 Maintenance Pack Install Guide) should be followed.
Keep in mind, on a 32-bit server, anything above ~800 MB in any given app pool will have adverse affects on performance and functionality. On a 64-bit server, this is raised to ~1800 MB.
We are currently working on a capacity planning guide that will outline this information and more. In it, we have defined an app pool distribution that serves as a good starting point. However, every customer is different, so this should be modified based on your environment and needs.