Skip to content
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

High Memory utilization in Asp.net core 2.2 #6831

Closed
ankitmori14 opened this issue Jan 18, 2019 · 5 comments
Closed

High Memory utilization in Asp.net core 2.2 #6831

ankitmori14 opened this issue Jan 18, 2019 · 5 comments
Assignees

Comments

@ankitmori14
Copy link

ankitmori14 commented Jan 18, 2019

Hi,

I have created just simple default application still i have't add any piece of code still it is utilizing 167 MB of memory.

Version : Asp.net Core 2.2

I am using Hosting Model : Default.

core2 2_blank_sol

My blank application is also using 167 MB of memory .

As you can see in screen shot.

  1. Microsoft.CodeAnalysis.PEModule it is utilizing high memory though i am not using any feature of it.
  2. Dictionary<String, ValueTuple<Int32, Int32>> same i am not using this also.

Please help my application is dying in production or i should move to .Net Framework
thanks in advance

@sebastienros
Copy link
Member

This looks like an expected behavior if you have more than 256MB of memory and are running with one code.

How much memory is available on the server?

my application is dying in production

Can you be more specific?

@sebastienros sebastienros self-assigned this Jan 18, 2019
@sebastienros
Copy link
Member

Also please read this thread: #3409
Thanks

@ankitmori14
Copy link
Author

ankitmori14 commented Jan 21, 2019

This looks like an expected behavior if you have more than 256MB of memory and are running with one code.

How much memory is available on the server?

my application is dying in production

Can you be more specific?

we have 32 GB of memory with load balancer.

@ankitmori14
Copy link
Author

Also please read this thread: #3409
Thanks

Yes i have go though this article. Can i share anything which can help you to troubleshoot the issue.

@sebastienros
Copy link
Member

I don't think there is any issue with the behavior, what you are describing is by design.

You can use the Workstation GC mode if you don't want the GC to be gready.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
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