SLURM - Revision history

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:36:12Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:36, 26 May 2026
Line 329:		Line 329:
	:: Asking for less of Mufasa's time improves your FairShare		:: Asking for less of Mufasa's time improves your FairShare

	; ~~Test~~ and ~~debug your~~ code using less powerful QOSes before running it on more powerful QOSes		; Debug and test code using less powerful QOSes before running it with more powerful QOSes
	:: Your test jobs will get a higher priority and your FairShare will improve		:: Your test jobs will get a higher priority and your FairShare will improve

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:35:02Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:35, 26 May 2026
Line 332:		Line 332:
	:: Your test jobs will get a higher priority and your FairShare will improve		:: Your test jobs will get a higher priority and your FairShare will improve

	; Cancel jobs ~~when~~ you don't need them anymore		; Cancel jobs that you don't need them anymore
	:: ~~Use~~ [[User_Jobs#Cancelling_a_job_with_scancel\|scancel]] to delete ~~your jobs when finished~~ (or if crashed ~~due to a bug~~): your Fairshare will improve		:: Always use [[User_Jobs#Cancelling_a_job_with_scancel\|scancel]] to delete completed (or crashed) jobs: your Fairshare will improve
	\|}		\|}

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:33:06Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:33, 26 May 2026
Line 323:		Line 323:
	:: 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 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 ~~--> priority of your future jobs~~		:: Asking for fewer CPUs and/or less RAM improves your FairShare

	; Do not request more time than your jobs needs to complete		; Do not request more time than your jobs needs to complete
	:: Make a worst-case estimate and only ask for that duration		:: Make a worst-case estimate and only ask for that duration
	:: Asking for less of Mufasa's time improves your FairShare ~~--> priority of your future jobs~~		:: Asking for less of Mufasa's time improves your FairShare

	; Test and debug your code using less powerful QOSes before running it on more powerful QOSes		; Test and debug your code using less powerful QOSes before running it on more powerful QOSes

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:32:50Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:32, 26 May 2026
Line 323:		Line 323:
	:: 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 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 --> priority of your future jobs

	; Do not request more time than your jobs needs to complete		; Do not request more time than your jobs needs to complete
	:: Make a worst-case estimate and only ask for that duration		:: Make a worst-case estimate and only ask for that duration
	:: Asking for less of Mufasa's time improves your FairShare		:: Asking for less of Mufasa's time improves your FairShare --> priority of your future jobs

	; Test and debug your code using less powerful QOSes before running it on more powerful QOSes		; Test and debug your code using less powerful QOSes before running it on more powerful QOSes

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:30:20Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:30, 26 May 2026
Line 336:		Line 336:
	\|}		\|}

	Protip: ~~if you're going to run a job,~~ it's a good idea to [[User Jobs#Looking for unused GPUs\|~~look~~ for unused GPUs]] before choosing what ~~GPU~~ to request. ~~Choosing~~ a GPU that is currently idle ~~should~~ help your job get ~~run~~ sooner.		Protip: it's a good idea to [[User Jobs#Looking for unused GPUs\|check for unused GPUs]] before choosing what to request. Requesting a GPU that is currently idle will help your job get executed sooner.

	= SLURM partitions =		= SLURM partitions =

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:28:48Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:28, 26 May 2026
Line 336:		Line 336:
	\|}		\|}

	~~Suggestion~~: if you're going to run a job, it's a good idea to [[#Looking for unused GPUs\|look for unused GPUs]] before choosing what GPU to request. Choosing a GPU that is currently idle should help your job get run sooner.		Protip: if you're going to run a job, it's a good idea to [[User Jobs#Looking for unused GPUs\|look for unused GPUs]] before choosing what GPU to request. Choosing a GPU that is currently idle should help your job get run sooner.

	= SLURM partitions =		= SLURM partitions =

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:28:02Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:28, 26 May 2026
Line 320:		Line 320:
	:: QOSes with access to less resources have higher base priority		:: QOSes with access to less resources have higher base priority

	; Only request CPUs and RAM that your job ~~will actually use~~		; 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 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

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:27:46Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:27, 26 May 2026
Line 322:		Line 322:
	; Only request CPUs and RAM that your job will actually use		; Only request CPUs and RAM that your job will actually use
	:: 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 designed to do so: if unsure, only ask for 1 CPU
	:: ~~If you ask for more RAM than needed,~~ your job ~~has to wait~~ for it ~~to be~~ 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

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:26:10Z

How to maximise the priority of your jobs

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

	; Only request CPUs and RAM that your job will actually use		; Only request CPUs and RAM that your job will actually use
	:: ~~If you didn't design your~~ code ~~to exploit~~ multiple CPUs~~, check that it does! If it doesn't~~, only ask for 1 CPU		:: Usually, code exploits multiple CPUs only if designed to do so: if unsure, only ask for 1 CPU
	:: If you ask for more RAM than needed, your job has to wait for it to be available		:: If you ask for more RAM than needed, your job has to wait for it to be available
	:: Asking for fewer CPUs and/or less RAM improves your FairShare		:: Asking for fewer CPUs and/or less RAM improves your FairShare

GiulioFontana: /* How to maximise the priority of your jobs */

2026-05-26T11:24:29Z

How to maximise the priority of your jobs

← Older revision		Revision as of 11:24, 26 May 2026
Line 323:		Line 323:
	:: If you didn't design your code to exploit multiple CPUs, check that it does! If it doesn't, only ask for 1 CPU		:: If you didn't design your code to exploit multiple CPUs, check that it does! If it doesn't, only ask for 1 CPU
	:: If you ask for more RAM than needed, your job has to wait for it to be available		:: If you ask for more RAM than needed, your job has to wait for it to be available
	:: Asking ~~many~~ CPUs and/or ~~much~~ RAM ~~lowers~~ your FairShare		:: Asking for fewer CPUs and/or less RAM improves your FairShare

	; Do not request more time than your jobs needs to complete		; Do not request more time than your jobs needs to complete
	:: Make a worst-case estimate and only ask for that duration		:: Make a worst-case estimate and only ask for that duration
	:: Asking for ~~much~~ of Mufasa's time ~~lowers~~ your FairShare		:: Asking for less of Mufasa's time improves your FairShare

	; Test and debug your code using less powerful QOSes before running it on more powerful QOSes		; Test and debug your code using less powerful QOSes before running it on more powerful QOSes