initial implementation of oom callback trigger mechanism #996
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a runtime heap allocation monitor which allows the application to watch the allocated heap size at regular intervals (which can be set and changed at will), with registered callback functions triggered any time the heap goes past each of a set of user-defined thresholds. The callback function is passed the threshold limit (which allows the same callback to be used for multiple thresholds) and the full set of runtime memory stats (not just the heap size), which the callback function may use to report memory telemetry to New Relic and/or take corrective action, as appropriate.