| 100 | | The "normal" QOS is intended for users running parallel programs. This is the preferred type of usage to best take advantage of Cypess's parallel processing capability. Each user is limited to simultaneous usage of 18 nodes (360 cores) over all his/her jobs. |
| 101 | | |
| 102 | | The "long" QOS is intended for jobs which are not very parallel, but have longer runtime. Each job has a job-size limit of 168 node-hours, calculated as the number of nodes requested multiplied by number of hours requested. For example a job submitted to the long QOS may request 1 node for 7 days, or 2 nodes for 3.5 days. You are limited to 8 nodes across all your jobs in this QOS. So, for example, you may run up to 8 jobs each using 1 node and running for 7 days. |
| 103 | | |
| 104 | | The "interactive" QOS is intended to be used for testing SLURM script submission, and is limited to 1 job per user. See [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#interactiveQOS|interactiveQOS] |
| | 100 | The "'''normal'''" QOS is intended for users running parallel programs. This is the preferred type of usage to best take advantage of Cypess's parallel processing capability. Each user is limited to simultaneous usage of 18 nodes (360 cores) over all his/her jobs. |
| | 101 | |
| | 102 | The "'''long'''" QOS is intended for jobs which are not very parallel, but have longer runtime. Each job has a job-size limit of 168 node-hours, calculated as the number of nodes requested multiplied by number of hours requested. For example a job submitted to the long QOS may request 1 node for 7 days, or 2 nodes for 3.5 days. You are limited to 8 nodes across all your jobs in this QOS. So, for example, you may run up to 8 jobs each using 1 node and running for 7 days. |
| | 103 | |
| | 104 | The "'''interactive'''" QOS is intended to be used for testing SLURM script submission, and is limited to 1 job per user. See [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#interactiveQOS interactiveQOS] |
