%systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/applicationPools /applicationPoolDefaults.startMode:"AlwaysRunning" /commit:apphost %systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/applicationPools /toStart:"True" /commit:apphost Then, we need to set the start mode to “AlwaysRunning” instead of the default “OnDemand” %systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/applicationPools /:00:00:00 /commit:apphost To disable the auto-recycle, run this command: %systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/applicationPools /:00:00:00 /commit:apphostĪlso, IIS will recycle an app pool after very 29 hours (1740 minutes). This results in sub-ideal user experience. The user will then have to wait for the spin up to complete before receiving the response. Once the node does receive the request, it will have to spin up the ASP.NET Core app, which takes some time. In a web farm scenario, for one reason or another, you can have a node that did not receive a request in a span of 20 minutes. The setting is called “Idle Time-Out (mintues)”. NET Framework 4.7.1)įirstly, IIS is configured to shut down a process after x minutes of inactivity. (Steps below were tested on Win 2016, IIS 10, running ASP.NET Core 2.0.1 with. By default, there are several settings in IIS which would cause issues in Production for high-load applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |