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.

Sign up for GitHub

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

Jump to bottom

MemoryMetricsSelector is using wrong metric value #6205

Open
Arkatufus opened this issue Oct 20, 2022 · 1 comment
Open

MemoryMetricsSelector is using wrong metric value #6205

Arkatufus opened this issue Oct 20, 2022 · 1 comment
Labels
confirmed bug

Comments

@Arkatufus
Copy link
Contributor

Version Information
Version of Akka.NET? All
Which Akka.NET Modules? Akka.Cluster.Metrics

Describe the bug
Based on our investigation in #4142 we found that Process.MaxWorkingSet is reporting erroneous values. This value is being used in the MemoryMetricsSelector

Expected behavior
MemoryMetricsSelector should be using the "committed heap metrics" that is not available before netcoreapp3.1.
The correct way of doing this is to use the "gc-heap-committed" metrics from the EventCounters API

Actual behavior
Process.MaxWorkingSet always returns 1.34 megabyte, a very useless value.
@Aaronontheweb
Copy link
Member

Plan is to roll this fix into v1.4, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
confirmed bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Aaronontheweb @Arkatufus