User Jobs - Revision history

GiulioFontana: /* Key concept: use containers! */

2026-07-20T14:42:08Z

Key concept: use containers!

← Older revision		Revision as of 14:42, 20 July 2026
Line 218:		Line 218:
	== Key concept: use containers! ==		== Key concept: use containers! ==

	'''~~The key concept about executing jobs on Mufasa is that~~ [[System#Containers\|~~all~~ computation on Mufasa must occur within containers]]'''.		'''[[System#Containers\|All computation on Mufasa must occur within containers]]'''.

	A container is a “sandbox” containing the environment where the user's application operates. Parts of Mufasa's filesystem can be made visible (and writable, if the user has writing permission on them: e.g., the user's <code>/home</code> directory) to the environment of the container. This allows the containerized user application to read from, and write to, Mufasa's filesystem: for instance, to read data and write results.		A container is a “sandbox” containing the environment where the user's application operates. Parts of Mufasa's filesystem can be made visible (and writable, if the user has writing permission on them: e.g., the user's <code>/home</code> directory) to the environment of the container. This allows the containerized user application to read from, and write to, Mufasa's filesystem: for instance, to read data and write results.

GiulioFontana: /* Key concept */

2026-07-20T14:41:43Z

Key concept

← Older revision		Revision as of 14:41, 20 July 2026
Line 216:		Line 216:
	= Executing jobs on Mufasa =		= Executing jobs on Mufasa =

	== Key concept ==		== Key concept: use containers! ==

	'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.		'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.

GiulioFontana: /* Key concept: use containers! */

2026-07-20T14:24:42Z

Key concept: use containers!

← Older revision		Revision as of 14:24, 20 July 2026
Line 216:		Line 216:
	= Executing jobs on Mufasa =		= Executing jobs on Mufasa =

	== Key concept~~: use containers!~~ ==		== Key concept ==

	'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.		'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.

GiulioFontana: /* Key concept */

2026-07-20T14:10:18Z

Key concept

← Older revision		Revision as of 14:10, 20 July 2026
Line 216:		Line 216:
	= Executing jobs on Mufasa =		= Executing jobs on Mufasa =

	== Key concept ==		== Key concept: use containers! ==

	'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.		'''The key concept about executing jobs on Mufasa is that [[System#Containers\|all computation on Mufasa must occur within containers]]'''.

GiulioFontana at 11:54, 27 May 2026

2026-05-27T11:54:01Z

← Older revision		Revision as of 11:54, 27 May 2026
Line 359:		Line 359:
	== Cancelling completed jobs ==		== Cancelling completed jobs ==

	When a user process run via SLURM has completed its execution and is not needed anymore, it is important to [[~~User_Jobs~~#~~Canceling_a_job_with_scancel~~\|close it with scancel]]. Especially if much time remains to the end of the execution time requested by the job.		When a user process run via SLURM has completed its execution and is not needed anymore, it is important to [[#Cancelling a job with scancel\|close it with scancel]]. Especially if much time remains to the end of the execution time requested by the job.

	Cancelling a SLURM job makes the resources reserved by SLURM free again for other users, and thus speeds up the execution of the jobs still queued.		Cancelling a SLURM job makes the resources reserved by SLURM free again for other users, and thus speeds up the execution of the jobs still queued.

GiulioFontana at 11:13, 26 May 2026

2026-05-26T11:13:58Z

← Older revision		Revision as of 11:13, 26 May 2026
Line 366:		Line 366:

	Please note that [[System#Job priority\|job priority]] for your user depends (also) on the overall duration of the jobs that you ran on Mufasa. Therefore, '''cancelling jobs that are not needed anymore improves your future jobs' priority'''.		Please note that [[System#Job priority\|job priority]] for your user depends (also) on the overall duration of the jobs that you ran on Mufasa. Therefore, '''cancelling jobs that are not needed anymore improves your future jobs' priority'''.

			= Looking for unused GPUs =

			GPUs are usually the most limited resource on Mufasa. So, if your job requires a GPU, the best way to get it executed quickly is to use a QOS associated to a type of GPU of which there are one or more that aren't currently in use. This command

			<pre style="color: lightgrey; background: black;">
			sinfo -O Gres:100
			</pre>

			provides a summary of all the Gres (i.e., GPU) resources possessed by Mufasa. It provides an output similar to the following:

			<pre style="color: lightgrey; background: black;">
			GRES
			gpu:40gb:3,gpu:4g.20gb:5,gpu:3g.20gb:5
			</pre>

			To know which of the GPUs are currently in use, use command

			<pre style="color: lightgrey; background: black;">
			sinfo -O GresUsed:100
			</pre>

			which provides an output similar to this:

			<pre style="color: lightgrey; background: black;">
			GRES_USED
			gpu:40gb:2(IDX:0-1),gpu:4g.20gb:2(IDX:5,8),gpu:3g.20gb:3(IDX:3-4,6)
			</pre>

			By comparing the two lists (GRES and GRES_USED) you can easily spot unused GPUs.

	= Detaching from a running job with <code>screen</code> =		= Detaching from a running job with <code>screen</code> =

GiulioFontana: /* Knowing what jobs you ran today */

2026-05-13T13:59:56Z

Knowing what jobs you ran today

← Older revision		Revision as of 13:59, 13 May 2026
Line 699:		Line 699:
	</pre>		</pre>

	provides a list of all ~~jobs run~~ by your user after yesterday's midnight. For each job, the command provides the start and end time and the command you used to run it (if needed, you can increase the value after <code>SubmitLine%-</code> to show longer commands in full).		provides a list of all <code>srun</code> or <code>sbatch</code> commands executed by your user after yesterday's midnight. For each job, the command provides the start and end time and the command you used to run it (if needed, you can increase the value after <code>SubmitLine%-</code> to show longer commands in full).

GiulioFontana: /* Knowing what jobs you ran today */

2026-05-13T13:58:51Z

Knowing what jobs you ran today

← Older revision		Revision as of 13:58, 13 May 2026
Line 699:		Line 699:
	</pre>		</pre>

	provides a list of all jobs run by your user after yesterday's midnight. For each job, the command provides the start and end time and the command you used to run it.		provides a list of all jobs run by your user after yesterday's midnight. For each job, the command provides the start and end time and the command you used to run it (if needed, you can increase the value after <code>SubmitLine%-</code> to show longer commands in full).

GiulioFontana: /* Knowing what jobs you ran today */

2026-05-13T13:57:32Z

Knowing what jobs you ran today

← Older revision		Revision as of 13:57, 13 May 2026
Line 696:		Line 696:

	<pre style="color: lightgrey; background: black;">		<pre style="color: lightgrey; background: black;">
	sacct -X		sacct -X --format=User%-10,Start,End,SubmitLine%-100
	</pre>		</pre>

	provides a list of all jobs run by your user after yesterday's midnight.		provides a list of all jobs run by your user after yesterday's midnight. For each job, the command provides the start and end time and the command you used to run it.

GiulioFontana: /* Knowing what jobs you ran today */

2026-05-13T13:55:56Z

Knowing what jobs you ran today

← Older revision		Revision as of 13:55, 13 May 2026
Line 699:		Line 699:
	</pre>		</pre>

	provides a list of all jobs run ~~today~~ by your user.		provides a list of all jobs run by your user after yesterday's midnight.