Increased memory consumption after upgrading to .NET 7

[mihaimyh]

After upgrading my applications to the latest .NET version (7.0.202), I have noticed a significant increase in memory consumption on Linux (RHEL7). Both my apps upgraded to .NET7 are self-contained.

Applying the fix described at #79633 (comment) (setting DOTNET_GCName=libclrgc.so) solved my problem and the memory consumption got reduced to the .NET 6 levels.

Please guide on how to collect traces from RHEL from both my applications I've upgraded.

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

Issue Details

---

After upgrading my application to the latest .NET version (7.0.202), I have noticed a significant increase in memory consumption on Linux (RHEL7).

Applying the fix described in #79633 (setting DOTNET_GCName=libclrgc.so) solved my problem and the memory consumption got reduced to the .NET 6 levels.

Author:	mihaimyh
Assignees:	-
Labels:	tenet-performance, area-GC-coreclr
Milestone:	-

[mangod9]

Could you please try the latest servicing release (7.0.4), and check if that makes things better? 7.0.3 has the fix for #79633.

[mihaimyh]

@mangod9 SDK 7.0.202 doesn't included 7.0.4 runtime?

[mangod9]

Oh sorry misread that as the runtime version. Yeah SDK 7.0.202 should be the latest. To investigate your issue if you have a standalone repro which shows the working set difference that would be great. Else if you could please collect GC only traces with default and the DOTNET_GCName config, that would help with investigating further. Thx!

This issue has been marked needs-author-action and may be missing some important information.

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.