User Tools

Site Tools


doku:vsc4_queue

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
doku:vsc4_queue [2021/09/14 12:46]
goldenberg [Quality of service (QOS)]
doku:vsc4_queue [2021/09/14 12:54] (current)
goldenberg [sbatch parameters]
Line 29: Line 29:
  
 The <html><font color=#cc3300>&#x27A0; devel queue</font></html> (devel_0096) gives fast feed-back to the user if her or his job is running. It is possible to connect to the node where the actual job is running and to directly [[doku:monitoring|monitor]] the job, e.g., for the purpose of checking if the threads/processes are doing what is expected. This might be recommended before sending the job to one of the 'computing' queues.  The <html><font color=#cc3300>&#x27A0; devel queue</font></html> (devel_0096) gives fast feed-back to the user if her or his job is running. It is possible to connect to the node where the actual job is running and to directly [[doku:monitoring|monitor]] the job, e.g., for the purpose of checking if the threads/processes are doing what is expected. This might be recommended before sending the job to one of the 'computing' queues. 
 +
 +==== Run time limits ====
 +
 +
 +^ The QOS's hard run time limits ^   |
 +| | | 
 +| mem_0096 / mem_0384 / mem_0768           | 72h (3 days) |           
 +| idle_0096 / idle_0384 / idle_0768        | 24h (1 day)  |
 +| private queues   p....._0...             | up to 240h (10 days) |
 +| devel_0096 (up to 5 nodes available)     | 10min        |
 +The QOS's run time limits can also be requested via the command
 +<code>sacctmgr show qos  format=name%20s,priority,grpnodes,maxwall,description%40s</code>
 +SLURM allows for setting a run time limit //below// the default QOS's run time limit. After the specified time is elapsed, the job is killed:
 +<code>#SBATCH --time=<time> </code>
 +Acceptable time formats include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and "days-hours:minutes:seconds".
 +
 +==== sbatch parameters ====
 +For submitting jobs, three parameters are important:
 +
 +<code>
 +#SBATCH --partition=mem_xxxx
 +#SBATCH --qos=xxxxx_xxxx
 +#SBATCH --account=xxxxxx
 +</code>
 +The core hours will be charged to the specified account. If not specified, the default account (''sacctmgr show user `id -u` withassoc format=defaultaccount'') will be used.
 +
 +=== ordinary projects ===
 +
 +For ordinary projects the QOSs are:
 +^QOS name ^ gives access to partition ^description^
 +| | | 
 +|mem_0096 | mem_0096 | default |
 +|mem_0384 | mem_0384 | |
 +|mem_0768 | mem_0768 | |
 +|devel_0096 | 5 nodes on mem_0096 |
 +
 +== examples ==
 +<code>
 +#SBATCH --partition=mem_0096
 +#SBATCH --qos=mem_0096   
 +#SBATCH --account=p7xxxx   
 +</code>
 +  * Note that partition, qos, and account have to fit together. 
 +  * If the account is not given, the default account (''sacctmgr show user `id -u` withassoc format=defaultaccount'') will be used.
 +  * If partition and qos are not given, default values are mem_0096 for both.
 +
 +=== private nodes projects ===
 +
 +== example ==
 +
 +<code>
 +#SBATCH --partition=mem_0384
 +#SBATCH --qos=p7xxx_xxxx
 +#SBATCH --account=p7xxxx 
 +</code> 
 +
 +
doku/vsc4_queue.1631623575.txt.gz ยท Last modified: 2021/09/14 12:46 by goldenberg