You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've found it useful in our environment to have munged lock its pages upon startup because our compute nodes are often subject to extreme memory and disk pressure. Without locking, munged sometimes gets swapped out and cannot respond to requests quickly enough. This causes the resource manager (slurm in our case) to believe that compute nodes are down when they really aren't.
I've written a patch (attached) that adds an option (-M, --mlockall) to munged so that it will lock pages on startup. It works well in our environment, so I thought it might be useful to others.
We've found it useful in our environment to have munged lock its pages upon startup because our compute nodes are often subject to extreme memory and disk pressure. Without locking, munged sometimes gets swapped out and cannot respond to requests quickly enough. This causes the resource manager (slurm in our case) to believe that compute nodes are down when they really aren't.
I've written a patch (attached) that adds an option (
-M
,--mlockall
) to munged so that it will lock pages on startup. It works well in our environment, so I thought it might be useful to others.0001-Add-mlockall-option-to-munged.patch.gz
Original issue reported on code.google.com by
michaelfenn87
on 22 Apr 2013 at 4:26The text was updated successfully, but these errors were encountered: