Mufasa (BioHPC) - Recent changes [en]

User Jobs

GiulioFontana — Mon, 20 Jul 2026 14:42:08 GMT

Key concept: use containers!

← Older revision		Revision as of 14:42, 20 July 2026
(2 intermediate revisions by the same user not shown)
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.

Users

GiulioFontana — Mon, 20 Jul 2026 14:17:50 GMT

Usernames and group names

← Older revision		Revision as of 14:17, 20 July 2026
Line 18:		Line 18:

	= Usernames and group names =		= Usernames and group names =
	Mufasa usernames have the form <code>xyyyyyyyy</code> (all lowercase), where <code>x</code> is the first letter of the first name of the person, and <code>yyyyyyyy</code> is their surname (or ~~part~~ of it if it's too long). For instance, a person called Giuseppe Brambilla will be assigned username <code>gbrambill</code>.		Mufasa usernames have the form <code>xyyyyyyyy</code> (all lowercase), where <code>x</code> is the first letter of the first name of the person, and <code>yyyyyyyy</code> is their surname (or the first 8 characters of it if it's too long). For instance, a person called Giuseppe Brambilla will be assigned username <code>gbrambill</code>.

	On Linux machines, users belong to ''groups''. On Mufasa, groups are used to identify research groups. Assigment of Mufasa's users to groups follow these rules:		On Linux machines, users belong to ''groups''. On Mufasa, groups are used to identify research groups. Assigment of Mufasa's users to groups follow these rules:

User Jobs

GiulioFontana — Mon, 20 Jul 2026 14:10:18 GMT

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]]'''.

SLURM

GiulioFontana — Mon, 20 Jul 2026 14:05:55 GMT

How to maximise the priority of your jobs

← Older revision		Revision as of 14:05, 20 July 2026
(6 intermediate revisions by the same user not shown)
Line 37:		Line 37:
	</pre>		</pre>

	which provides an output similar to the following:		which provides an output similar to the following (see below for the same data in table form):

	<pre style="color: lightgrey; background: black;">		<pre style="color: lightgrey; background: black;">
Line 97:		Line 97:
	! max # of</br>4g.20GB</br>GPUs		! max # of</br>4g.20GB</br>GPUs
	! max # of</br>40GB</br>GPUs		! max # of</br>40GB</br>GPUs
	~~! MinTRES</br>(GPUs)~~
	\|-		\|-
	! rowspan="1" style="text-align:center;" \| build		! rowspan="1" style="text-align:center;" \| build
Line 105:		Line 104:
	\| 2		\| 2
	\| 16		\| 16
	~~\| -~~
	\| -		\| -
	\| -		\| -
Line 116:		Line 114:
	\| 2		\| 2
	\| 64		\| 64
	\| 1		\| 1 (min=1)
	\| -		\| -
	\| -		\| -
	~~\| one 3g.20GB~~
	\|-		\|-
	! rowspan="1" style="text-align:center;" \| nogpu		! rowspan="1" style="text-align:center;" \| nogpu
Line 127:		Line 124:
	\| 16		\| 16
	\| 128		\| 128
	~~\| -~~
	\| -		\| -
	\| -		\| -
Line 138:		Line 134:
	\| 8		\| 8
	\| 64		\| 64
	\| 1		\| 1 (min=1)
	\| -		\| -
	\| -		\| -
	~~\| one 3g.20GB~~
	\|-		\|-
	! rowspan="1" style="text-align:center;" \| gpuwide		! rowspan="1" style="text-align:center;" \| gpuwide
Line 150:		Line 145:
	\| 64		\| 64
	\| -		\| -
	\| 1		\| 1 (min=1)
	\| -		\| -
	~~\| one 4g.20GB~~
	\|-		\|-
	! rowspan="1" style="text-align:center;" \| gpuheavy-20		! rowspan="1" style="text-align:center;" \| gpuheavy-20
Line 161:		Line 155:
	\| 128		\| 128
	\| -		\| -
	\| 2		\| 2 (min=1)
	\| -		\| -
	~~\| one 4g.20GB~~
	\|-		\|-
	! rowspan="1" style="text-align:center;" \| gpuheavy-40		! rowspan="1" style="text-align:center;" \| gpuheavy-40
Line 173:		Line 166:
	\| -		\| -
	\| -		\| -
	\| 1		\| 1 (min=1)
	~~\| one 40GB~~
	\|}		\|}

	A key piece of information in the table above is the '''priority tier''' associated to each QOS.		A key piece of information in the table above is the '''priority tier''' associated to each QOS. In Mufasa 2.0, priority tiers are used to encourage users to use the '''least powerful QOS that is compatible with their needs''', where "powerful" means "rich with resources". Less powerful QOSes increase the priority of the jobs that use them, so these jobs tend to be executed sooner. See [[#Job priority\|Job priority]] for details about how priority affects the execution order of jobs in Mufasa 2.0.

	In Mufasa 2.0, priority tiers are used to encourage users to use the '''least powerful QOS that is compatible with their needs''', where "powerful" means "rich with resources". Less powerful QOSes increase the priority of the jobs that use them, so these jobs tend to be executed sooner. See [[#Job priority\|Job priority]] for details about how priority affects the execution order of jobs in Mufasa 2.0.

	== The <code>build</code> QOS ==		== The <code>build</code> QOS ==
Line 197:		Line 187:
	= <code>research</code> users and <code>students</code> users =		= <code>research</code> users and <code>students</code> users =

	Users of Mufasa belong to two '''user categories'''. Categories provide users with different access to to Mufasa's resources: the idea being to provide researchers with more access while still letting students ~~use~~ the server.		Users of Mufasa belong to two '''user categories'''. Categories provide users with different access to to Mufasa's resources: the idea being to provide researchers with more access while still letting students benefit from the server's capabilities.

	User categories in Mufasa are the following:		User categories in Mufasa are the following:
Line 305:		Line 295:
	#* '''RAM''' - impact on FairShare is proportional to the amount of RAM used		#* '''RAM''' - impact on FairShare is proportional to the amount of RAM used
	#* '''GPUs''' - impact on FairShare is proportional to the number of GPUs used		#* '''GPUs''' - impact on FairShare is proportional to the number of GPUs used
	#** 40 GB GPUs have double the impact on FairShare than 20 GB GPUs		#** note: 40 GB GPUs have double the impact on FairShare than 20 GB GPUs
	# The impact on FairShare of any use of resources is '''proportional to its duration'''		# The impact on FairShare of any use of resources is '''proportional to its duration'''
	#* example: using 32 GB of RAM for 48h has the same impact of using 64 GB of RAM for 24h		#* example: using 32 GB of RAM for 48h has the same impact of using 64 GB of RAM for 24h
Line 321:		Line 311:

	; Only request CPUs and RAM that your job really needs		; Only request CPUs and RAM that your job really needs
	:: Usually, code exploits multiple CPUs only if designed to do so: if unsure, only ask for 1 CPU		:: Usually, code exploits multiple CPUs only if specifically designed to do so: if unsure, only ask for 1 CPU
	:: The fewer resources your job asks for, the less it will wait before they become available		:: The fewer resources your job asks for, the less it will wait before they become available
	:: Asking for fewer CPUs and/or less RAM improves your FairShare		:: Asking for fewer CPUs and/or less RAM improves your FairShare