Skip to main content

List Process IDs (PIDs) for your IIS Application Pools

One of our production servers started to send out alerts because the memory consumption was too high. A first look at the server showed us that one of the w3wp processes was consuming most of the available resources on the server.

 


Sidenote: Web applications running within Microsoft’s Internet Information Services (IIS) utilize what is known as IIS worker processes. These worker processes run as w3wp.exe, and there are typically multiple per server.

So we knew that one of our web applications was causing trouble. The question of course now is which one?

As the resource manager only showed us the process id, we couldn’t immediately give the answer. But with some extra command line magic we got the answer.

To get the information we need we used the appcmd utility. This tool allows; among other things; to list the IIS worker processes.

We executed appcmd list wps and got the the list of worker processes with their PIDs.

c:\Windows\System32\inetsrv>appcmd list wps

WP "46848" (applicationPool:BerichtenBox Services)

WP "23640" (applicationPool:ird3graphql)

WP "35632" (applicationPool:VervoerSvc)

WP "28616" (applicationPool:MailService)

WP "46452" (applicationPool:DefaultAppPool)

WP "12612" (applicationPool:arno)

WP "29144" (applicationPool:BIG)

WP "15388" (applicationPool:Toa)

WP "46208" (applicationPool:DocumentStorageServices)

WP "35716" (applicationPool:auth3services)

Now it was easy to map the process id to the correct application pool. Next step is to further investigate why this application was causing such high memory usage but that is maybe for another post…

More information

What is w3wp.exe? - IIS Worker Process Explained (stackify.com)

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

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