-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASP NET Core project, memory growing. Is GC configured correctly? #1627
Comments
The first course of action would be to get a memory dump and analyze it using either visual studio, windbg, perfview or other familiar tools. |
Stop sending me emails On July 2, 2016, at 23:59, David Fowler notifications@github.com wrote: The first course of action would be to get a memory dump and analyze it using either visual studio, windbg, perfview or other familiar tools. You are receiving this because you are subscribed to this thread. |
Thanks, I'll keep it in mind. After a few days of observation, I've noticed that under normal condition the application memory working set can vary a lot, slowly growing and shrinking even by 400MB. There were some abnormal situations when trying to POST some large JSON documents (5MB doc) caused huge increases in memory usage even if they were not specifically parsed or required as part of the controller method parameters (I'll submit another question regarding this). I suspect they are caused by some part of the system buffering data. |
In code, you can inspect GCSettings.IsServerGC |
Hi,
I've deployed an ASP NET Core project (.net 4.6.1 as framework) on Azure Web App and I see a continuously growing memory footprint. It seems that every request slowly grows the working set of the app and I really don't know what to do. My first idea is that GC is not working as expected. Here is what happens over time. Any suggestion is welcome, thanks!
Here is my project configuration. Notice GC is enabled as a runtimeObject:
I also have an app.config setup and deployed in the approot folder:
The text was updated successfully, but these errors were encountered: