Changes between Version 5 and Version 6 of cypress/about
- Timestamp:
- 01/13/15 09:13:58 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
cypress/about
v5 v6 65 65 || '''QOS name''' || '''maximum job size (node-hours)''' || '''walltime''' || '''maximum nodes per user''' || 66 66 || interactive || N/A || 4 hours || 1 || 67 || normal || 288 || 24 hours || 24||67 || normal || N/A || 24 hours || 12 || 68 68 || long || 168 || 168 hours || 8 || 69 69 70 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 job has a job-size limit of 288 node-hours, calculated as the number of nodes requested multiplied by number of hours requested. For example a job submitted to the normal QOS may request 12 nodes for 24 hours, or 24 nodes for 12 hours. Regardless of job size, each user is limited to simultaneous usage of 24 nodes (480 cores) over all his/her jobs.70 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 12 nodes (240 cores) over all his/her jobs. 71 71 72 The "long" QOS is intended for jobs which are not very parallel, but have longer runtime. The maximum walltime for the job is 168 hours (7 days), and the job size is limited to 168 node-hours. So, for example, a jobmay request 1 node for 7 days, or 2 nodes for 3.5 days.72 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. 73 73 74 74 The "interactive" QOS is intended to be used for testing SLURM script submission, and is limited to 1 node and 4 hours.