Recycling Settings for an Application Pool Specific Times: Set to the least used time of the day:.Regular time interval (minutes): 0 (set to zero).Or set "Idle time-out action" to "Suspend".Do not leave recycling configuration as default:.If your server is domain-joined and if your application needs to access resources over network, consider using "group managed service accounts" (gMSA):.Use ApplicationPoolIdentity as identity.Even if you have such a limitation, try to resolve it. Use 64bit application pools if you do not have a limitation by any of the modules your application uses.If your application does not work in Integrated mode, use Classic mode until you resolve the issue. You might consider grouping applications to pools if there are too many applications and/or sites (hundreds, thousands) hosted, for administration and management purposes only. Create one application pool for each application.Therefore, do not expect the below list to address and resolve all your problems. They can only be as secure and as performant as your code. One more thing before we get to my recommendations: Keep in mind that web servers are just hosting platforms for your applications. Especially some of the performance best practices listed below would help you keep your cloud costs as low as possible. Most of the below mentioned settings or recommendations apply to the web applications hosted on cloud solutions (like Azure Web Apps) and some will already be in-place. For such cases, consider your applications specific needs and decide accordingly. It may be possible that you will find some resources mentioning just the opposite of what I say. I should say that these are my own thoughts based on my own experience. Having these said, I tried to gather a list of things one should check while configuring an IIS server (and an application on IIS). Therefore, in many cases, you will not have one universal best practice. A web server is just a hosting platform for applications, and, each and every application has its own needs. Actually, the main problem here is that there cannot be “best practices” for a web server.
There are some blogs/articles on the Internet, but I could not find a complete one. Hope you enjoy it :)įor a very long time, I have been asked for a document on IIS best practices. NET Core a new HTTP version… And after eight more years of experience on a variety of customers and environments, finally I thought it was time for an update. During this time, several new versions of IIS have arrived, some reached end of lifecycle we were introduced a new development platform called. It has been almost eight years since I first wrote a blog on IIS best practices.
0 kommentar(er)
