Apply hibernate_after option to all applicable processes
#78
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.
CubDB can be configured with the
hibernate_afteroption to reduce memory usage when idle. However, this option is currently only applied to the mainCubDBprocess. Other processes started by CubDB can also accumulate memory, and applyinghibernate_afterto them can further minimise memory usage when they are idle.This PR applies the
hibernate_afteroption to all applicable processes started by CubDB:1.
CubDB.Store.File: This process can hold references to large binaries that have been written to file and may not be garbage collected while idle.2.
CubDB.CleanUp: Although I have not seen this process holding significant memory,hibernate_afterhas been applied just in case it does, and to maintain consistency with other CubDB processes.3.
Task.Supervisor: Supervisors do not support thehibernate_afteroption, so this option is not applied to this process.