Skip to content
This repository has been archived by the owner on Dec 19, 2018. It is now read-only.

Question : IIS dotnet.exe memory management #900

Closed
onesandzeros415 opened this issue Dec 8, 2016 · 1 comment
Closed

Question : IIS dotnet.exe memory management #900

onesandzeros415 opened this issue Dec 8, 2016 · 1 comment

Comments

@onesandzeros415
Copy link

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.

dotnetmem

Any clarification on memory/cpu management of the dotnet.exe process via IIS would be helpful.

@Tratcher
Copy link
Member

Tratcher commented Dec 8, 2016

This issue was moved to aspnet/AspNetCoreModule#51

@Tratcher Tratcher closed this as completed Dec 8, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants