IIS: Idle Timeout vs Recycle

by

Idle Timeout is if no action has been asked from your web app, it the process will drop and release everything from memory

Recycle is a forced action on the application where your processed is closed and started again, for memory leaking purposes and system health

The negative impact of both is usually the use of your Session and Application state is lost if you mess with Recycle to a faster time.(logged in users etc will be logged out, if they where about to “check out” all would have been lost” that’s why recycle is at such a large time out value, idle timeout doesn’t matter because nobody is logged in anyway and figure 20 minutes an no action they are not still “shopping”

The positive would be get rid of the idle time out as your website will respond faster on its “first” response if its not a highly active site where a user would have to wait for it to load if you have 1 user every 20 minutes lets say. So a website that get his less then 1 time in 20 minutes actually you would want to increase this value as the website has to load up again from scratch for each user. but if you set this to 0 over a long time, any memory leaks in code could over a certain amount of time, entirely take over the server.

More Related Contents:

  1. Best way to run scheduled tasks [closed]
  2. What causes an application pool in IIS to recycle?
  3. Access-control-allow-origin with multiple domains
  4. Where does Console.WriteLine go in ASP.NET?
  5. What are all the user accounts for IIS/ASP.NET and how do they differ?
  6. Losing Session State
  7. HTTP Error 503, the service is unavailable
  8. IIS7 Cache-Control
  9. ASP.NET Web API OperationCanceledException when browser cancels the request
  10. HTTP Error 403.14 – Forbidden – The Web server is configured to not list the contents of this directory
  11. IIS Request Timeout on long ASP.NET operation
  12. ASP.NET Core with IIS – HTTP Verb Not Allowed
  13. How can I share a session across multiple subdomains in ASP.NET?
  14. How to debug w3wp clr.dll error
  15. Web Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
  16. How to keep ASP.NET assemblies in AppDomain alive?
  17. HTTP Error 500.22 – Internal Server Error (An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.)
  18. Caching specific Javascript and CSS files
  19. What is limiting the # of simultaneous connections my ASP.NET application can make to a web service?
  20. NuGet: ‘X’ already has a dependency defined for ‘Y’
  21. How to deliver big files in ASP.NET Response?
  22. double escape sequence inside a url : The request filtering module is configured to deny a request that contains a double escape sequence
  23. IIS7 – The request filtering module is configured to deny a request that exceeds the request content length
  24. ASP.NET 5 project hosting on IIS
  25. Script not served by static file handler on IIS7.5
  26. What does ‘IISReset’ do?
  27. SignalR and Browser Connection limit
  28. Diagnosing 404 errors on IIS 7 and ASP.NET MVC
  29. What is an IIS application pool?
  30. How do I make a “generic error” page in my ASP.NET application so that it handles errors triggered when serving that page itself?

Leave a Comment