These are my thoughts on the matter, so it's best to perform your own research and arrive at your own conclusion. While it can be extreme, recycling should not be used to "resolve" a resource leak or a hang. If you are on an environment that is limited in resource and host multiple sites, then I can see recycling/throttling to best use resources. However, let's pretend I build a windows service instead of a website on IIS for a company. If my service would hang when running for 24 hours or would consume all the memory in a server and I don't state that in the specifications, asking to schedule a task to restart the service every 29 hours probably won't be acceptable to some customers and they would ask me to fix that. Well, that is what recycling is doing. Of course it brings a new worker process up before terminating the old one, but you will see the effects of a cold start of a worker process. Hence, I would recommend testing how the site runs without recycling or the idle-timeout and adjust accordingly.