Handling large collections of files: Difference between revisions

Jump to navigation Jump to search
Line 63: Line 63:
* <code>/tmp</code> is cleared at job end
* <code>/tmp</code> is cleared at job end
* like all of a job's other memory use, falls under the cgroup limit corresponding to the sbatch request
* like all of a job's other memory use, falls under the cgroup limit corresponding to the sbatch request
* we set the tmpfs size via mount options at 100%, which could potentially confuse some scripts, since it means /tmp's size is shown as the node's MemTotal. For example, df reports /tmp size as the physical RAM size, which does not correspond to the sbatch request
* we set the tmpfs size via mount options at 100%, which could potentially confuse some scripts, since it means <code>/tmp</code>'s size is shown as the node's MemTotal. For example, <code>df</code> reports <code>/tmp</code> size as the physical RAM size, which does not correspond to the <code>sbatch</code> request


==Archiving == <!--T:8-->
==Archiving == <!--T:8-->
cc_staff
318

edits

Navigation menu