Batch Jobs - bwUniCluster Features: Difference between revisions
No edit summary |
|||
| Line 35: | Line 35: | ||
<br> |
<br> |
||
<br> |
<br> |
||
= Environment Variables for Batch Jobs = |
|||
The bwUniCluster expands the [[Batch_Jobs#Environment Variables for Batch Jobs|common set of MOAB environment variables]] by the following variable(s): |
|||
{| style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px" |
|||
! colspan="3" style="background-color:#999999;padding:3px"| bwUniCluster specific MOAB variables |
|||
|- style="width:25%;height=20px; text-align:left;padding:3px" |
|||
! style="width:20%;height=20px; text-align:left;padding:3px"| Environment variables |
|||
! style="height=20px; text-align:left;padding:3px"| Description |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | MOAB_SUBMITDIR |
|||
| style="height=20px; text-align:left;padding:3px"| Directory of job submission |
|||
|} |
|||
<br> |
|||
Since the work load manager MOAB on [[bwUniCluster]] uses the resource manager SLURM, the following environment variables of SLURM are added to your environment once your job has started: |
|||
{| style="width:100%; vertical-align:top; background:#f5fffa;border:1px solid #000000;padding:1px" |
|||
! colspan="3" style="background-color:#999999;padding:3px"| SLURM variables |
|||
|- style="width:25%;height=20px; text-align:left;padding:3px" |
|||
! style="width:20%;height=20px; text-align:left;padding:3px"| Environment variables |
|||
! style="height=20px; text-align:left;padding:3px"| Description |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_CPUS_PER_NODE |
|||
| style="height=20px; text-align:left;padding:3px"| Number of processes per node dedicated to the job |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_NODELIST |
|||
| style="height=20px; text-align:left;padding:3px"| List of nodes dedicated to the job |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_JOB_NUM_NODES |
|||
| style="height=20px; text-align:left;padding:3px"| Number of nodes dedicated to the job |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_MEM_PER_NODE |
|||
| style="height=20px; text-align:left;padding:3px"| Memory per node dedicated to the job |
|||
|- |
|||
| style="width:20%;height=20px; text-align:left;padding:3px" | SLURM_NPROCS |
|||
| style="height=20px; text-align:left;padding:3px"| Total number of processes dedicated to the job |
|||
|} |
|||
<br> |
|||
<br> |
|||
= Interactive Jobs = |
|||
Interactive jobs on bwUniCluster [[BwUniCluster_User_Access#Allowed_activities_on_login_nodes|must '''NOT''' run on the logins nodes]], however resources for interactive jobs can be requested using msub. Considering a serial application with a graphical frontend that requires 5000 MByte of memory and limiting the interactive run to 2 hours execute the following: |
|||
<pre> |
|||
$ msub -I -V -l nodes=1:ppn=1 -l walltime=0:02:00:00 |
|||
</pre> |
|||
The option -V defines that all environment variables are exported to the compute node of the interactive session. |
|||
After execution of this command '''DO NOT CLOSE''' your current terminal session but wait until the queueing system MOAB has granted you the requested resources on the compute system. Once granted you will be automatically logged on the dedicated resource. Now you have an interactive session with 1 core and 5000 MByte of memory on the compute system for 2 hours. Simply execute now your application: |
|||
<pre> |
|||
$ cd to_path |
|||
$ ./application |
|||
</pre> |
|||
Note that, once the walltime limit has been reached you will be automatically logged out of the compute system. |
|||
<br> |
|||
<br> |
|||
---- |
|||
[[Category:bwUniCluster|Batch Jobs - bwUniCluster features]] |
|||
Revision as of 16:55, 21 July 2014
This article contains information on features of the batch job system only applicable on bwUniCluster.
Job Submission
msub Command
msub -l resource_list
No deviation or additional features to general batch job setting.
msub -q queues
| msub -q queue | ||
|---|---|---|
| queue | maximum resources | |
| -q develop | walltime=00:30:00 (i.e. 30 min), node=1, processes=16 | |
| -q singlenode | walltime=3:00:00:00 (i.e. 3 days), node=1, processes=16 | |
| -q multinode | walltime=2:00:00:00 (i.e. 2 days), node=8 | |
| -q verylong | walltime=6:00:00:00 (i.e. 6 days), node=1, processes=16 | |
| -q fat | walltime=1:00:00:00 (i.e. 1 day), node=1, processes=32 on fat nodes | |
- To run your batch job longer than 3 days, please use$ msub -q verylong.
- To run your batch job on one of the fat nodes, please use$ msub -q fat.
Environment Variables for Batch Jobs
The bwUniCluster expands the common set of MOAB environment variables by the following variable(s):
| bwUniCluster specific MOAB variables | ||
|---|---|---|
| Environment variables | Description | |
| MOAB_SUBMITDIR | Directory of job submission | |
Since the work load manager MOAB on bwUniCluster uses the resource manager SLURM, the following environment variables of SLURM are added to your environment once your job has started:
| SLURM variables | ||
|---|---|---|
| Environment variables | Description | |
| SLURM_JOB_CPUS_PER_NODE | Number of processes per node dedicated to the job | |
| SLURM_JOB_NODELIST | List of nodes dedicated to the job | |
| SLURM_JOB_NUM_NODES | Number of nodes dedicated to the job | |
| SLURM_MEM_PER_NODE | Memory per node dedicated to the job | |
| SLURM_NPROCS | Total number of processes dedicated to the job | |
Interactive Jobs
Interactive jobs on bwUniCluster must NOT run on the logins nodes, however resources for interactive jobs can be requested using msub. Considering a serial application with a graphical frontend that requires 5000 MByte of memory and limiting the interactive run to 2 hours execute the following:
$ msub -I -V -l nodes=1:ppn=1 -l walltime=0:02:00:00
The option -V defines that all environment variables are exported to the compute node of the interactive session. After execution of this command DO NOT CLOSE your current terminal session but wait until the queueing system MOAB has granted you the requested resources on the compute system. Once granted you will be automatically logged on the dedicated resource. Now you have an interactive session with 1 core and 5000 MByte of memory on the compute system for 2 hours. Simply execute now your application:
$ cd to_path $ ./application
Note that, once the walltime limit has been reached you will be automatically logged out of the compute system.