Add memory monitoring to livereduce #15
Merged
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.
Ref: 6960: [LIVEREDUCTION] Add memory monitoring
It works by creating function running in it's own thread that is checking the memory usage. If it gets above the set percentage it will stop live data, clear the workspaces and restart live data. This seemed like a better solution then running mantid in a subprocess, MonitorLiveData is already running in it's own thread anyway.
To test I created another example in the test folder using
FakeISISEventDAE
where it's producing lots of events and the proceeding will just accumulated all the events quickly using up the available memory.Start the fake server
start livereduce
and you should see live data getting restarted after it uses 25% of your memory.