You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
I apologize if this is a duplicate question however I've yet to find any concrete information on IIS dotnet.exe memory/cpu management. According to @DamianEdwards from September 17, 2015 via issue 364 IIS is still managing the process. The AppPool settings that control recycling, memory limits, etc. still apply.
Does this apply to limiting memory/cpu consumption of the dotnet.exe process itself? I'm curious as I've set a memory limit of 524 megabytes on an application pool and dotnet.exe is able to exceed this set limit. Setting process affinity also does not appear to work on the dotnet.exe process.
Any clarification on memory/cpu management of the dotnet.exe process via IIS would be helpful.
The text was updated successfully, but these errors were encountered:
I apologize if this is a duplicate question however I've yet to find any concrete information on IIS dotnet.exe memory/cpu management. According to @DamianEdwards from September 17, 2015 via issue 364 IIS is still managing the process. The AppPool settings that control recycling, memory limits, etc. still apply.
Does this apply to limiting memory/cpu consumption of the dotnet.exe process itself? I'm curious as I've set a memory limit of 524 megabytes on an application pool and dotnet.exe is able to exceed this set limit. Setting process affinity also does not appear to work on the dotnet.exe process.
Any clarification on memory/cpu management of the dotnet.exe process via IIS would be helpful.
The text was updated successfully, but these errors were encountered: