Modify nersc_controller to avoid getting OOM killed #272
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.
Checking up at NERSC on the LTA components, I saw this as an active problem in the logs:
I tried to manually run
/usr/bin/squeue --json
and was greeted with a long pause, followed by 45+ seconds of JSON output.This command grabs metadata for all the jobs recently run, running, or about to be run in all of SLURM. That's a huge list.
This PR adds the
--me
flag to the command, which I tested. The result is generated almost immediately, and weighed in at 49655 bytes. If we mind our own business and inquire about our own jobs, it should speed up the execution of the nersc-controller, and prevent it from getting OOM killed.