-
Notifications
You must be signed in to change notification settings - Fork 66
[ML] Track memory usage in CHierarchicalResultsNormalizer #2831
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
[ML] Track memory usage in CHierarchicalResultsNormalizer #2831
Conversation
…g and limits integration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just the one comment regarding test case naming.
…ment/2244-hierarchical-normalizer
…d include necessary headers
…ed EMPTY_STRING constant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing major. I think there are some small clean ups possible and I left a question. Otherwise, LGTM
…in CHierarchicalResultsNormalizer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (aside the build issue)
… CHierarchicalResultsLevelSet
… and CHierarchicalResultsLevelSet
|
@wwang500 , this PR should lead to an increase in reported memory usage on jobs with a large number of partitions/influencers. Can you please verify this with the nightly runs? |
This PR makes CHierarchicalResultsNormalizer to track its memory usage. Fixes elastic#2244
This PR makes CHierarchicalResultsNormalizer to track its memory usage.
Fixes #2244