Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:services:application_services:high_performance_computing:running_jobs_slurm [2019/06/18 10:52]
tehlers
en:services:application_services:high_performance_computing:running_jobs_slurm [2020/04/14 14:47] (current)
mboden [''sbatch'': Specifying node properties with ''-C'']
Line 28: Line 28:
  
 **MPI job**\\ **MPI job**\\
-A Job with distributed memory parallelization,​ realized with MPI. Can use several job slots on several nodes and needs to be started with ''​mpirun''​ or substitute.+A Job with distributed memory parallelization,​ realized with MPI. Can use several job slots on several nodes and needs to be started with ''​mpirun''​ or the Slurm substitute ​''​srun''​.
  
 **Partition**\\ **Partition**\\
Line 46: Line 46:
  
 **medium**\\ **medium**\\
-This is our general purpose partition, usable for serial and SMP jobs with up to 20 tasks, but it is especially well suited for large MPI jobs. Up to 1024 cores can be used in a single MPI job, and the maximum runtime is 48 hours.+This is our general purpose partition, usable for serial and SMP jobs with up to 24 tasks, but it is especially well suited for large MPI jobs. Up to 1024 cores can be used in a single MPI job, and the maximum runtime is 48 hours.
  
 **fat**\\ **fat**\\
-This is the partition for SMP jobs, especially those requiring lots of memory. Serial jobs with very high memory requirements do also belong in this partition. Up to 64 cores and 256 GB are available on one host. Maximum runtime is 48 hours.+This is the partition for SMP jobs, especially those requiring lots of memory. Serial jobs with very high memory requirements do also belong in this partition. Up to 64 cores and up to 512 GB are available on one host. Maximum runtime is 48 hours.\\ 
 +The nodes of the fat+ partitions are also present in this partition, but will only be used, if they are not needed for bigger jobs submitted to the fat+ partition.
  
 **fat+**\\ **fat+**\\
-This partition is meant for very memory intensive jobs. For more details see below (**fat-fas+** and **fat-fmz+**).+This partition is meant for very memory intensive jobs. These partitions are for jobs that require ​more than 512 GB RAM on single node. Nodes of fat+ partitions have 1.5 and 2 TB RAM. You are required to have specify your memory needs on job submission to use these nodes (see [[en:​services:​application_services:​high_performance_computing:​running_jobs_slurm#​resource_selection|resource selection]]).\\ 
 +As general advice: Try your jobs on the smaller nodes in the fat partition first and work your way up and don't be afraid to ask for help here.
  
-These are called '​meta'​ partitions, because they are just collections +**gpu** - A partition for nodes containing GPUs. Please refer to [[en:​services:​application_services:​high_performance_computing:​running_jobs_slurm#​gpu_selection]] ​
-of different partitions.\\ +
-If you need more fine grained control over the on which kind of nodes your job runs, you can also directly use the underlying '​real'​ partitions:​\\ +
-**medium-fas** - Medium ​nodes at Faßberg\\ +
-**medium-fmz** - Medium nodes at the Fernmeldezentrale\\ +
-**fat-fas** - Fat nodes at Faßberg\\ +
-**fat-fmz** - Fat nodes at the Fernmeldezentrale+
  
-**fat-fas+** and **fat-fmz+**\\ +====  ​Runtime limits (QoS)  ====
-These partitions are for jobs that require more than 256 GB RAM on single node. Nodes of fat+ partitions have 512 GB, 1.5 and 2 TB RAM. Due to limited amount of such nodes, there are restrictions of using the partition, which you can find at the [[en:​services:​application_services:​high_performance_computing:​running_jobs_for_experienced_users#​using_the_fat_partitions|page for experienced Users]]  +
- +
-**gpu** - A partition for nodes containing GPUs. Please refer to INSERT STUFF HERE +
- +
-====  ​Available QOS  ====+
 If the default time limits are not sufficient for your jobs, you can use a "​Quality of Service"​ or **QOS** to modify those limits on a per job basis. We currently have two QOS. If the default time limits are not sufficient for your jobs, you can use a "​Quality of Service"​ or **QOS** to modify those limits on a per job basis. We currently have two QOS.
  
Line 81: Line 72:
 Interactively or in batch mode. We generally recommend using the Interactively or in batch mode. We generally recommend using the
 batch mode. If you need to run a job interactively,​ you can find batch mode. If you need to run a job interactively,​ you can find
-information about that LINK.+information about that in the [[en:​services:​application_services:​high_performance_computing:​running_jobs_slurm#​interactive_session_on_the_nodes|corresponding section]].
 Batch jobs are submitted to the cluster using the '​sbatch'​ command Batch jobs are submitted to the cluster using the '​sbatch'​ command
 and a jobscript or a command:\\ and a jobscript or a command:\\
Line 93: Line 84:
  
 ====  "​sbatch"​ options ​ ==== ====  "​sbatch"​ options ​ ====
 +
 +**<​nowiki>​-A all</​nowiki>​**\\
 +Specifies the account '​all'​ for the job. This option is //​mandatory//​ for users who have access to special hardware and want to use the general partitions.
  
 **<​nowiki>​-p <​partition></​nowiki>​**\\ **<​nowiki>​-p <​partition></​nowiki>​**\\
Line 106: Line 100:
 **<​nowiki>​-o <​file></​nowiki>​**\\ **<​nowiki>​-o <​file></​nowiki>​**\\
 Store the job output in "​file"​ (otherwise written to slurm-<​jobid>​). ''​%J''​ in the filename stands for the jobid.\\ Store the job output in "​file"​ (otherwise written to slurm-<​jobid>​). ''​%J''​ in the filename stands for the jobid.\\
 +
 +**<​nowiki>​--noinfo</​nowiki>​**\\
 +Some metainformation about your job will be added to your output file. If you do not want that, you can suppress it with this flag.\\
 +
 +**<​nowiki>​--mail-type=[ALL|BEGIN|END]</​nowiki>​\\
 +<​nowiki>​--mail-user=your@mail.com</​nowiki>​** \\
 +Receive mails when the jobs start, end or both. There are even more options, refer to the sbatch man-page for more information about mail types. If you have a GWDG-mail-address,​ you do not need to specify the mail-user.\\
  
 ====  Resource Selection ​ ==== ====  Resource Selection ​ ====
Line 116: Line 117:
 **<​nowiki>​-c <cpus per task></​nowiki>​**\\ **<​nowiki>​-c <cpus per task></​nowiki>​**\\
 The number of cpus per tasks. The default is one cpu per task. The number of cpus per tasks. The default is one cpu per task.
 +
 +**<​nowiki>​-c vs -n</​nowiki>​**\\
 +As a rule of thumb, if you run your code on a single node, use -c. For multi-node MPI-jobs, use -n.\\
  
 **<​nowiki>​-N <​minNodes[,​maxNodes]></​nowiki>​**\\ **<​nowiki>​-N <​minNodes[,​maxNodes]></​nowiki>​**\\
Line 132: Line 136:
  
 **<​nowiki>​--mem-per-cpu=<​size[units]></​nowiki>​**\\ **<​nowiki>​--mem-per-cpu=<​size[units]></​nowiki>​**\\
-Required memory per task instead of node. <​nowiki>​--mem</​nowiki>​ and <​nowiki>​--mem-per-cpu</​nowiki> ​is mutually exclusive\\+Required memory per task instead of node. <​nowiki>​--mem</​nowiki>​ and <​nowiki>​--mem-per-cpu</​nowiki> ​are mutually exclusive.\\
 === Example === === Example ===
  
Line 152: Line 156:
 **-C scratch[2]**\\ **-C scratch[2]**\\
 The node must have access to shared ''/​scratch''​ or ''/​scratch2''​. The node must have access to shared ''/​scratch''​ or ''/​scratch2''​.
 +
 +**-C fmz / -C fas**\\
 +The node has to be at that location. It is pretty similar to -C scratch / -C scratch2, since the nodes in the FMZ have access to scratch and those at the Fassberg location have access to  scratch2. This is mainly for easy compatibility with our old partition naming scheme.
 +
 +**-C [architecture]**\\
 +request a specific CPU architecture. Available Options are: abu-dhabi, ivy-bridge, haswell, broadwell. See [[en:​services:​application_services:​high_performance_computing:​start#​hardware_overview|this table]] for the corresponding nodes.
  
  
 ====  Using Job Scripts ​ ==== ====  Using Job Scripts ​ ====
  
-A job script is a shell script with a special comment section: In each line beginning with ''#​SBATCH''​ the following text is interpreted as a ''​sbatch''​ option. Here is an example:+A job script is a shell script with a special comment section: In each line beginning with ''#​SBATCH''​ the following text is interpreted as a ''​sbatch''​ option. These options have to be at the top of the script before any other commands are executed. Here is an example:
  
 <​code>​ <​code>​
Line 188: Line 198:
 <​code>​ <​code>​
 export OMP_NUM_THREADS=4 export OMP_NUM_THREADS=4
-sbatch --exclusive -p mpi -N 2 --ntasks-per-node=4 --wrap="​mpirun ./​hybrid_job"​+sbatch --exclusive -p medium ​-N 2 --ntasks-per-node=4 --wrap="​mpirun ./​hybrid_job"​
 </​code>​ </​code>​
 (each MPI process creates 4 OpenMP threads in this case). (each MPI process creates 4 OpenMP threads in this case).
Line 254: Line 264:
 ==== GPU selection ==== ==== GPU selection ====
  
-In order to use a GPU you should submit your job to the ''​gpu''​ partition, and request GPU count and optionally the model. CPUs of the nodes in gpu partition are evenly distributed for every GPU. So if you are requesting a single GPU on the node with 20 cores adn 4 GPUs, you can get up to 5 cores reserved exclusively for you, the same is with memory. So for example, if you want 2 GPUs of model Nvidia GeForce GTX 1080 with 10 CPUs, you can submit a job script with the following flags: +In order to use a GPU you should submit your job to the ''​gpu''​ partition, and request GPU count and optionally the model. CPUs of the nodes in gpu partition are evenly distributed for every GPU. So if you are requesting a single GPU on the node with 20 cores and 4 GPUs, you can get up to 5 cores reserved exclusively for you, the same is with memory. So for example, if you want 2 GPUs of model Nvidia GeForce GTX 1080 with 10 CPUs, you can submit a job script with the following flags: 
-<​code> ​+<​code>​
 #SBATCH -p gpu #SBATCH -p gpu
 #SBATCH -n 10 #SBATCH -n 10
-#SBATCH --gres=gpu:gtx1080:2+#SBATCH -gtx1080:2
 </​code>​ </​code>​
  
-You can also omit the model selection, here is an example of selecting 1 GPU of any available model: + 
-<​code>​+You can also omit the model selection, here is an example of selecting 1 GPU of any available model:<​code>​
 #SBATCH -p gpu #SBATCH -p gpu
 #SBATCH -n 10 #SBATCH -n 10
-#SBATCH --gres=gpu:1+#SBATCH -1
 </​code>​ </​code>​
 +
 +There are different options to select the number of GPUs, such as ''​%%--gpus-per-node%%'',​ ''​%%--gpus-per-task%%''​ and more. See the [[https://​slurm.schedmd.com/​sbatch.html|sbatch man page]] for details.
  
 Currently we have several generations of NVidia GPUs in the cluster, namely: Currently we have several generations of NVidia GPUs in the cluster, namely:
Line 279: Line 291:
 <​code>​ <​code>​
 #SBATCH -p gpu #SBATCH -p gpu
-#SBATCH --gres=gpu:k40:2+#SBATCH -k40:2
 </​code>​ </​code>​
 Our Tesla K40 are of the Kepler generation. Our Tesla K40 are of the Kepler generation.
Line 285: Line 297:
 <​code>​ sinfo -p gpu --format=%N,​%G </​code>​ shows a list of host with GPUs, as well as their type and count. <​code>​ sinfo -p gpu --format=%N,​%G </​code>​ shows a list of host with GPUs, as well as their type and count.
  
-=====  ​Miscallaneous ​Slurm Commands ​ =====+=====  ​Miscellaneous ​Slurm Commands ​ =====
  
 While ''​sbatch''​ is arguably the most important Slurm command, you may also find the following commands useful: While ''​sbatch''​ is arguably the most important Slurm command, you may also find the following commands useful:
Line 303: Line 315:
 **<​nowiki>​sacct -j <​jobid>​ --format=JobID,​User,​UID,​JobName,​MaxRSS,​Elapsed,​Timelimit</​nowiki>​**\\ **<​nowiki>​sacct -j <​jobid>​ --format=JobID,​User,​UID,​JobName,​MaxRSS,​Elapsed,​Timelimit</​nowiki>​**\\
 Get job Information even after the job has finished.\\ Get job Information even after the job has finished.\\
-**Note on ''​sacct'':​** Depending on the parameters given ''​sacct''​ chooses a time window in a rather unintuitive way. This is documented in the DEFAULT TIME WINDOW section of its man page. If you unexpectedly get no results from your ''​sacct''​ query, try specifying the start time with, e.g. ''<​nowiki>​-S 2019-01-01</​nowiki>''​.+**Note on ''​sacct'':​** Depending on the parameters given ''​sacct''​ chooses a time window in a rather unintuitive way. This is documented in the DEFAULT TIME WINDOW section of its man page. If you unexpectedly get no results from your ''​sacct''​ query, try specifying the start time with, e.g. ''<​nowiki>​-S 2019-01-01</​nowiki>''​.\\ 
 +The ''<​nowiki>​--format</​nowiki>''​ option knows many more fields like **Partition**,​ **Start**, **End** or **State**, for the full list refer to the man page.
  
 **<​nowiki>​scancel</​nowiki>​**\\ **<​nowiki>​scancel</​nowiki>​**\\