I am configuring a new IIS web server for a low-to-medium traffic ASP.NET application and trying to optimize the Application Pool settings for performance and resource usage.

I noticed two settings that seem to shut down or restart worker processes (w3wp.exe):

• Idle Time-out (minutes): Set to 20 by default under Advanced Settings > Process Model.
• Recycling: Configured by default to trigger every 1740 minutes (29 hours).

My main concern is the cold start latency issue. When the site has not been accessed for 30 minutes, the first user experiences a 5 to 10 second delay because IIS terminated the worker process due to the Idle Time-out and must spin up a new process.

What are the exact operational differences between these two features? Is it safe to set Idle Time-out to 0 in production to keep the application continuously warm, or does that create long-term memory management problems?