<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>We've been running for years with out swap on with no issues. You
may want to set MemSpecLimit in your config to reserve memory for
the OS, so that way you don't OOM the system with user jobs:
<a class="moz-txt-link-freetext" href="https://slurm.schedmd.com/slurm.conf.html#OPT_MemSpecLimit">https://slurm.schedmd.com/slurm.conf.html#OPT_MemSpecLimit</a></p>
<p>-Paul Edmon-<br>
</p>
<div class="moz-cite-prefix">On 12/11/2023 11:19 AM, Davide DelVento
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAX1q8aRceieopwhMW755fPPgvhuUGgEhzJwY9nGj0R9jwoaWQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">A little late here, but yes everything Hans said is
correct and if you are worried about slurm (or other critical
system software) getting killed by OOM, you can workaround it by
properly configuring cgroup.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 6, 2023 at 2:06 AM
Hans van Schoot <<a href="mailto:vanschoot@scm.com"
moz-do-not-send="true" class="moz-txt-link-freetext">vanschoot@scm.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> Hi Joseph,<br>
<br>
This might depend on the rest of your configuration, but in
general swap should not be needed for anything on Linux.<br>
BUT: you might get OOM killer messages in your system logs,
and SLURM might fall victim to the OOM killer (OOM = Out Of
Memory) if you run applications on the compute node that eat
up all your RAM. <br>
Swap does not prevent against this, but makes it less likely
to happen. I've seen OOM kill slurm daemon processes on
compute nodes with swap, usually slurm recovers just fine
after the application that ate up all the RAM ends up
getting killed by the OOM killer. My compute nodes are not
configured to monitor memory usage of jobs. If you have
memory configured as a managed resource in your SLURM setup,
and you leave a bit of headroom for the OS itself (e.g. only
hand our a maximum of 250GB RAM to jobs on your 256GB RAM
nodes), you should be fine.<br>
<br>
cheers,<br>
Hans<br>
<br>
<br>
ps. I'm just a happy slurm user/admin, not an expert, so I
might be wrong about everything :-)<br>
<br>
<br>
<br>
<div>On 06-12-2023 05:57, John Joseph wrote:<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>Dear All, </div>
<div>Good morning </div>
<div>We have 4 node [256 GB Ram in each node]
SLURM instance with which we installed and it is
working fine. </div>
<div>We have 2 GB of SWAP space on each node, for
some purpose to make the system in full use want
to disable the SWAP memory, </div>
<div><br>
</div>
<div>Like to know if I am disabling the SWAP
partition will it efffect SLURM functionality . </div>
<div><br>
</div>
<div>Advice requested</div>
<div>Thanks </div>
<div>Joseph John </div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>