Skip to main content

Make your ASP.NET Core application always running on IIS

By default when running an ASP.NET Core application in IIS, the application will not be started until the first user hits your ASP.NET Core application. This of course saves some resources(CPU, memory,...) when no one is accessing your site, but comes with a performance penalty when the first request arrives.

A related feature exists where the application pool is shutdown after some idle time.

Although I think this is a good default it is not what we want when we have one or more background tasks running in our ASP.NET Core application. In these situations you want to have your ASP.NET Core application always running.

Let me walk you through the steps how to get this done.

Install IIS features

First check if you have the Application Initialization Module installed in IIS. If you are doing this on your local development machine, have a look at the list of Windows Features:

Otherwise you can install it through Server Manager:

  • Open the Add Roles and Features Wizard.
  • In the Select role services panel, open the Application Development node.
  • Select the checkbox for Application Initialization.

Configure IIS

Now we need to configure IIS. Start by opening the IIS Manager.

We start by configuring the Application pool:

  • Select Application Pools in the Connections panel.
  • Right-click the app's app pool in the list and select Advanced Settings.
  • The default Start Mode is OnDemand. Set the Start Mode to AlwaysRunning.
  • Also update the Idle Time-Out (minutes) to 0.
  • Select OK.

Now we need to also update the website to activate the preload feature:

  • Open the Sites node in the Connections panel.
  • Right-click the app and select Manage Website > Advanced Settings.
  • The default Preload Enabled setting is False. Set Preload Enabled to True.
  • Select OK.

    Configure your ASP.NET Core app

    There is not much you need to do at the level of your ASP.NET Core application. The only thing that is required is that your are using the In-Process hosting model which is the default.

    More information can be found at:

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
    Read more

    A complex system designed from scratch never works

    A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
    Read more