Iris partitions

Partition	Walltime	Purpose
interactive	<= 24 hours	For interactive jobs only
PI_interactive	<= 7 days	PI interactive jobs
cpushort	<= 2 hours	CPU short jobs
gpushort	<= 2 hours	GPU short jobs
cpu (default)	<= 7 days	CPU regular jobs
cpu_highmem	<= 7 days	Nodes with 4TB of RAM
gpu	<= 7 days	GPU regular jobs
chanj3	<= 7 days	PI buy-in resources
preemptable*	<= 7 days	Jobs can be preempted if resources needed in above partitions

*Intended for low-priority jobs that Slurm can stop to allow high-priority jobs to run; because of this, jobs submitted to the preemptable partition need to have checkpoints in place. For example, let's say I've designed a job with checkpoints, and I want it to run whenever a particular server type is available, but I'm okay with if Slurm needs to stop my job to let a high-priority job run. If a high-priority job is submitted by someone else (say, they have priority in their own partition for that server), since my job is preemptable, Slurm will stop my job and start the other user's. Once the resources become available again, my job will restart from the last checkpoint.

See more details here: https://github.mskcc.org/pages/HPC/userdocs/scheduler/slurm/partitions.html

partition limit

scontrol show partition <partition_name>

Group user limit

sacctmgr show assoc account=chanj3 format=User,Partition,Account,QOS,GrpTRES,MaxTRES,MaxJobs

Fairshare priority

sprio -u $USER