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

memory logging shows per-locale metrics #2728

Closed
hokiegeek2 opened this issue Aug 29, 2023 · 0 comments · Fixed by #2729
Closed

memory logging shows per-locale metrics #2728

hokiegeek2 opened this issue Aug 29, 2023 · 0 comments · Fixed by #2729
Assignees
Labels
bug Something isn't working

Comments

@hokiegeek2
Copy link
Contributor

Describe the bug
In researching a user-reported issue re: overMemLimit calculations I see that the logging is on a per-locale basis, which could be misleading. For example, for the Arkouda instance below, --memMax is set to 2GB for a three-node cluster, meaning that the total memory is 6 GB.

image

The logging should reflect that the numbers being reported are on a per-locale basis or the sum of total memory avail and total memory used by all locales and be consistent across all log statements.

ak.get_config() Output

image

@hokiegeek2 hokiegeek2 added the bug Something isn't working label Aug 29, 2023
@hokiegeek2 hokiegeek2 self-assigned this Aug 29, 2023
hokiegeek2 added a commit to hokiegeek2/arkouda that referenced this issue Aug 29, 2023
github-merge-queue bot pushed a commit that referenced this issue Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant