.NET Core 2.0 Kestrel Garbage Collection Concern

[antonellil]

All,

I am using .NET Core 2.0 in a Docker container via the microsoft/dotnet:2.0-sdk image on a Digital Ocean droplet running Docker 1.12.3 on Ubuntu 16.04, with 2GB of RAM and 2 CPUs.

Below is the memory timeline I am seeing from the past 6 hours, with around 120 users accessing the site in those 6 hours.

Below are the relevant portions of my .csproj and Program.cs files.

.csproj

Program.cs

I am using standard 2.0 Kestrel as provided in the CreateDefaultBuilder.

Any help would be extremely appreciated so I do not have to manually restart the docker image on server to reset the memory. I am aware that there is a Server Garbage Collection key that can be added to the csproj, but unsure if that could be the solution.

Thank you!

[antonellil]

Update:

Seems to have leveled off and is GC'ing correctly. But still very interesting behavior that would be good to get to the bottom of

[antonellil]

And.... it seems to have begun rising yet again. Definitely concerning.

[halter73]

@antonellil In case you're not seeing the back references, I want to point out that this might be caused by an issue reading cgroup limits described in dotnet/coreclr#13489

[antonellil]

@halter73 great find, yes this seems to be related