![]() We’ve seen how to work around the “cold-hit” problem that often affects websites running on IIS. Advanced Application Warm Up with Auto-Start The addition of the startMode attribute will override the default start mode of “ OnDemand“. Inside of the node, locate the entry whose name attribute corresponds to your application pool, and add a startMode attribute with the value of “ AlwaysRunning“. Inside of the nfig file, locate the node located under /. nfig can be found at \System32\inetsrv\config\nfig. ![]() In this case, we can also enable Auto-Start by tweaking the nfig file which controls the application domains for all instances running on that server. For example, imagine that you were rolling out your website to a large web server farm and need to automate the configuration of all your application pools. Configuration Auto-Start with nfigĮnabling Auto-Start using the IIS Manager UI is quick and simple, but tweaking the settings for all of your application pools via the user interface may not be scalable. That’s it! Now the website hosted by the application pool you just modified will always be instantly available, even after extended periods of activity. ![]() Locate the Start Mode option under the General group and set it to AlwaysRunning.Select the application pool for which you wish to enable Auto-Start.In the Connections pane, select the Application Pools node, revealing the Application Pools pane in the main view.Open Internet Information Services (IIS) Manager.Configuring Auto-Start with IIS ManagerĮnabling Auto-Start via IIS is actually quite simple, though the settings can be tricky to find the first time. In this article we’ll see how we can enable this feature either through IIS Manager or configuration files and even how we can perform more advanced application warm-up routines, such as priming a cache. In the simplest sense, enabling this feature causes IIS to prime an application as soon as it is deployed removing the warm-up time often required of “cold hits” to a website. Auto-Start, introduced with IIS 7.5, allows an ASP.NET application deployed to IIS to be available immediately after deployment. ![]() Since the site hasn’t been accessed yet, it must first be loaded by IIS before ASP.NET can properly respond to the request. It’s this lazy-loading of websites that causes the first request to an ASP.NET site to take so much longer than others. In fact, the AppDomain for a website on IIS is not loaded until its needed and, by default, will eventually be unloaded after a period of inactivity. That’s because to maximize resources IIS doesn’t keep all sites on an instance running at all times. Have you ever thought that the first request to your ASP.NET application seems to take much longer than others? If so, then you’re not imagining things…it actually does. This tip seemed to strike a chord with a few developers so I’ve decided to expand on it here. One of these was a little known tip on preventing the delay that commonly occurs from a cold hit on an ASP.NET website running on IIS. The book is full of quick and easy tips to squeeze some added performance from your ASP.NET applications, and if you haven’t had the chance to check it out yet you can download it for free from here.īeing a bit of a performance nut myself, I jumped at the opportunity to share a few tips of my own. The result was an excellent free e-book entitled “50 Ways to Avoid, Find and Fix ASP.NET Performance Issues”. Red Gate recently polled the ASP.NET developer community for tips on improving the performance of ASP.NET web applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |