Job <jobid> exceeded <mem> memory limit, being killed:
Your job is attempting to use more memory than you've requested for it. Either increase the amount of memory requested by
--mem-per-cpuor, if possible, reduce the amount your application is trying to use. For example, many Java programs set heap space using the
-Xmx JVM option. This could potentially be reduced.
For jobs that require truly large amounts of memory (>256 Gb), you may need to use the
bigmem SLURM partition. Genome and transcript assembly tools are commonly in this camp.
See this FAQ on determining how much memory your completed batch job used under SLURM.
Posted in: c. Jobs and SLURM
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Permissions beyond the scope of this license may be available at Attribution.