Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
GAMESS-US: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 126: | Line 126: | ||
<!--T:25--> | <!--T:25--> | ||
It is important to leave a few hundred MB of memory between the memory requested from the scheduler and the memory that GAMESS is allowed to use, as a safety margin. If the <code>slurm-{JOBID}.out</code> file contains a message like "slurmstepd: error: Exceeded step/job memory limit at some point",then Slurm has terminated the job for trying to use more memory than was requested. In that case one needs to either reduce the <code>MWORDS</code> or <code>MEMDDI</code> in the input file or increase the <code>--mem-per-cpu</code> in the submission script. | It is important to leave a few hundred MB of memory between the memory requested from the scheduler and the memory that GAMESS is allowed to use, as a safety margin. If a job's | ||
output is incomplete and the <code>slurm-{JOBID}.out</code> file contains a message like "slurmstepd: error: Exceeded step/job memory limit at some point",then Slurm has terminated the job for trying to use more memory than was requested. In that case one needs to either reduce the <code>MWORDS</code> or <code>MEMDDI</code> in the input file or increase the <code>--mem-per-cpu</code> in the submission script. | |||
== References == <!--T:26--> | == References == <!--T:26--> | ||