Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Using node-local storage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
When Slurm starts a job, it creates on each node assigned to the job a temporary directory. | When Slurm starts a job, it creates on each node assigned to the job a temporary directory. | ||
It then sets the full path name of | It then sets the full path name of that directory in an environment variable called <code>SLURM_TMPDIR</code>. | ||
Because this directory resides on local disk, input and output (I/O) to it | Because this directory resides on local disk, input and output (I/O) to it | ||
| Line 8: | Line 8: | ||
Any job doing substantial input and output (which is most jobs!) may expect | Any job doing substantial input and output (which is most jobs!) may expect | ||
to run more quickly if it uses <code>$SLURM_TMPDIR</code> instead of network disk. | to run more quickly if it uses <code>$SLURM_TMPDIR</code> instead of network disk. | ||
Specifically, local disk | Specifically, local disk is better for frequent small I/O transactions than network storage. | ||
transactions than network storage. | |||
The temporary character of <code>$SLURM_TMPDIR</code> makes somewhat more trouble to use than | The temporary character of <code>$SLURM_TMPDIR</code> makes somewhat more trouble to use than | ||