Program running memory is higher and higher, GC is not big, working set memory is large

[NlMay]

Description

There are many requests per second, gc0, GC1, GC2 are all small. It's just that the working set keeps growing,What causes this?

Configuration

CentOS Linux release 7.8.2003 (Core)
.NETCore 5.0

Regression?

Other information

Line chart：

Using global dotnet counters to analyze dotnet process:

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

There are many requests per second, gc0, GC1, GC2 are all small. It's just that the working set keeps growing,What causes this?

Configuration

CentOS Linux release 7.8.2003 (Core)
.NETCore 5.0

Regression?

Other information

Line chart：

Using global dotnet counters to analyze dotnet process:

Author:	NlMay
Assignees:	-
Labels:	area-GC-coreclr, untriaged
Milestone:	-

[Maoni0]

@sywhang recently made a change to expose committed bytes to counters. including him to see if he can give you a build of dotnet counters that show the committed bytes data. of course it may not have anything to do with the GC heap - committed would give the info to show whether that's the case or not.

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

There are many requests per second, gc0, GC1, GC2 are all small. It's just that the working set keeps growing,What causes this?

Configuration

CentOS Linux release 7.8.2003 (Core)
.NETCore 5.0

Regression?

Other information

Line chart：

Using global dotnet counters to analyze dotnet process:

Author:	NlMay
Assignees:	-
Labels:	area-Diagnostics-coreclr, area-GC-coreclr
Milestone:	-

[NlMay]

It was the working set that found the growth