Differences

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

--- doku:vsc3qos [2017/06/13 14:06] – [Quality of services defined on VSC-3] ir
+++ doku:vsc3qos [2017/06/13 14:31] – [Run time limits] ir
@@ Line 1: / Line 1: @@
 ====== QOS defined on VSC-3 ======
-Access to node partitions is granted by the so-called quality of service (QOS). The QOSs constrain the number of allocatable nodes and limit job wall time. The naming scheme of the QOSs is:
+Generally, it can be distinguished in QOS defined on the ordinary compute nodes (mem_0064/mem_0128/mem0256), on KNLs, on GPUs, 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
-<project_type>_<memoryConfig>
+in the <html><font color=#cc3300>&#x27A0; idle queue</font></html>.
-The QOSs that are assigned to a specific user can be viewed with:
-<code>
-sacctmgr show user `id -u` withassoc format=user,defaultaccount,account,qos%40s,defaultqos%20s
-</code>
+The <html><font color=#cc3300>&#x27A0; 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 ====
@@ Line 18: / Line 14: @@
 | private queues   p....._0...             | 240h (10 days) |
 | devel queue (up to 10 nodes available)   | 10min        |
+| GPU                                      |          |
+| KNL                                      |        |
 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>