Both sides previous revision Previous revision Next revision | Previous revision |
doku:vsc3_queue [2021/09/11 18:53] – [sbatch parameters] goldenberg | doku:vsc3_queue [2022/11/04 11:24] (current) – ↷ Links adapted because of a move operation 85.25.185.103 |
---|
| |
^partition name^ description^ | ^partition name^ description^ |
| | | | |
|vsc3plus_0064 | default, nodes with 64 GB of memory | | |vsc3plus_0064 | default, nodes with 64 GB of memory | |
|vsc3plus_0256 | nodes with 256 GB of memory| | |vsc3plus_0256 | nodes with 256 GB of memory| |
|binf | Bioinformatics nodes | | |binf | Bioinformatics nodes | |
|jupyter| reserved for the JupyterHub | | |jupyter| reserved for the JupyterHub | |
| |
| For the specific GPU partitions, see [[doku:vsc-gpuqos|GPUs on VSC-3]] |
| |
| The partitions of the oil-cooled nodes (normal_0064, normal_0128, normal_0256), the Xeon Phi nodes (knl) and the ARM nodes (arm) have been decommissioned and are no longer available. |
===== Quality of service (QOS) ===== | ===== Quality of service (QOS) ===== |
| |
Generally, it can be distinguished in QOS defined on the ordinary compute nodes (vsc4plus_0064/vsc3plus_0256), on GPUs, on Bioinformatics nodes and on private nodes. Furthermore, there is a distinction whether a project still has available computing time or if the computing time has already been consumed. In the latter case, jobs of this project are running with low job priority and reduced maximum run time limit in the <html><font color=#cc3300>➠ idle queue</font></html>. | Generally, it can be distinguished in QOS defined on the ordinary compute nodes (vsc4plus_0064/vsc3plus_0256), on GPUs, on Bioinformatics nodes and on private nodes. Furthermore, there is a distinction whether a project still has available computing time or if the computing time has already been consumed. In the latter case, jobs of this project are running with low job priority and reduced maximum run time limit in the <html><font color=#cc3300>➠ idle queue</font></html>. |
| |
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. | The <html><font color=#cc3300>➠ devel queue</font></html> (devel_0064) 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 ==== |
| |
| normal_binf | 24h (1 day) | | | normal_binf | 24h (1 day) | |
| private queues p....._0... | up to 240h (10 days) | | | private queues p....._0... | up to 240h (10 days) | |
| devel queue (up to 10 nodes available) | 10min | | | devel_0064 (up to 4 nodes available) | 10min | |
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> |
|vsc3plus_0256 | vsc3plus_0256| | | |vsc3plus_0256 | vsc3plus_0256| | |
|gpu_.... | gpu_xxxx|GPU QOS and GPU partition of the same name| | |gpu_.... | gpu_xxxx|GPU QOS and GPU partition of the same name| |
|normal_binf | binf| | |normal_binf | binf| | |
| |devel_0064 | 4 nodes on vsc3plus_0064 | |
| |
== examples == | == examples == |