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

Correct Extremem memory accounting tallies #52

Open
kdnilsen opened this issue Oct 7, 2020 · 0 comments
Open

Correct Extremem memory accounting tallies #52

kdnilsen opened this issue Oct 7, 2020 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@kdnilsen
Copy link
Contributor

kdnilsen commented Oct 7, 2020

Part of the computational workload shouldered by Extremem is to track the total allocations performed by each thread along with tracking when previously allocated objects should become eligible for garbage collection. These tallies are reported to standard output.

Nearly all objects allocated by Extremem are eventually supposed to be discarded. At certain critical execution points, the total number and flavors of certain object allocations should equal the total number and flavors of matching object discards. That these numbers do not currently match demonstrates that there are errors in the current calculations of these memory allocation and deallocation tallies.

We need to correct the tallies.

@kdnilsen kdnilsen added bug Something isn't working help wanted Extra attention is needed labels Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant