Skip to main content

Improve the startup performance of your .NET apps

In our continuous quest to improve the performance of our applications, I found the following ‘trick’ to improve the startup times of your application:

Add large assemblies to the NGen cache on the server

While profiling our ASP.NET applications, we noticed that some of them took a long time(>15 seconds) to render their first page after a cold start. The problem is that some of the assemblies used inside our application (I’m looking at you Entity Framework!) are quite large. Every time the application restarts, these large assemblies needs to JIT-ted.

To avoid the JIT cost, we can create a native image using ngen. The runtime can use these native images from the cache instead of using the just-in-time (JIT) compiler to compile the original assembly.

Let’s go through the steps:

  • Login on the server
  • Open an Administrator command prompt
  • Browse to the bin folder of one of the (slow) apps
  • Execute the following command for every DLL you want to add to the NGen cache:
    • "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe" install <dllname>.dll

You only need to do this for one applications as all apps will share the cached native image.

Note: don’t forget to measure before and after. It doesn’t make sense to do this for all assemblies.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

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         ...