This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision |
doku:vsc3qos [2017/06/13 14:27] – [QOS defined on VSC-3] ir | doku:vsc3qos [2017/06/13 14:31] – [Run time limits] ir |
---|
in the <html><font color=#cc3300>➠ idle queue</font></html>. | in the <html><font color=#cc3300>➠ idle queue</font></html>. |
| |
The <html><font color=#cc3300>➠ devel queue</font></html> has been setup in order that a user can test if her or his job is running before sending it to one of the 'computing' queues. 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 | The <html><font color=#cc3300>➠ devel queue</font></html> 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 ==== | ==== Run time limits ==== |
| |
| private queues p....._0... | 240h (10 days) | | | private queues p....._0... | 240h (10 days) | |
| devel queue (up to 10 nodes available) | 10min | | | devel queue (up to 10 nodes available) | 10min | |
| | GPU | | |
| | KNL | | |
The QOS's run time limits can also be requested via the command | 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> | <code>sacctmgr show qos format=name%20s,priority,grpnodes,maxwall,description%40s</code> |