Difference between revisions of "Default:Limits"
From CAC Wiki
(→Default Execution Limits) |
(→Default Execution Limits) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {| style="border-spacing: 8px;" | ||
| + | | valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#e1eaf1; border-radius:7px" | | ||
=Default Execution Limits= | =Default Execution Limits= | ||
| − | |||
Execution limits at the Centre for Advanced Computing are in place to provide greater flexibility in scheduling user applications. The following table shows the default limits that are currently in place. Note that our clusters are undergoing extensions and re-structuring, and that these limits are likely to change in the near future. Please check sporadically to keep up-to-date with them. | Execution limits at the Centre for Advanced Computing are in place to provide greater flexibility in scheduling user applications. The following table shows the default limits that are currently in place. Note that our clusters are undergoing extensions and re-structuring, and that these limits are likely to change in the near future. Please check sporadically to keep up-to-date with them. | ||
| − | + | {| class="wikitable" style="text-align: center; | |
| − | {| class="wikitable" style="text-align: | + | |
!colspan="3"| '''Disk Quota on User File Systems''' | !colspan="3"| '''Disk Quota on User File Systems''' | ||
|- | |- | ||
| Line 13: | Line 13: | ||
| All | | All | ||
| Global Job limit | | Global Job limit | ||
| − | | | + | | n/a |
|- | |- | ||
| SW (Linux) | | SW (Linux) | ||
| Process (thread) limit | | Process (thread) limit | ||
| − | | | + | | 80 |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
|} | |} | ||
| − | + | * '''Global Job Limit:''' At present we do '''not''' have any job limits, i.e. the scheduler will schedule all jobs that fit within the process limits (below) and the available hardware. | |
| − | + | * '''Process or Thread Limit:''' A maximum number of processes or threads that can be run at a given time is in place to cap standard jobs at the default allocation. The current value for the SW (Linux) Cluster is 80. This is a recent increase to compensate for the shutdown of our Solaris Servers. | |
| − | '''Important Note:''' Research groups will in many cases require more resources, especially in terms of thread/process numbers, and may fall outside of these limits. We will work with these users to ensure appropriate access. Any requests for enhanced access should include specifications for number of processors required, total amount of memory, and the expected maximum runtime(s). [ | + | '''Important Note:''' Research groups will in many cases require more resources, especially in terms of thread/process numbers, and may fall outside of these limits. We will work with these users to ensure appropriate access. Any requests for enhanced access should include specifications for number of processors required, total amount of memory, and the expected maximum runtime(s). [mailto:cac.help@queensu.ca Contact User Support] to ensure that this is arranged using the most appropriate resource. |
| − | + | '''Long-term extended usage''' requires a formal [https://www.computecanada.ca/research-portal/accessing-resources/resource-allocation-competitions/''' application to Compute Canada''']. Calls for such applications are currently issued once a year in the fall. We are announcing these calls on our web page. The allocation is done by a '''Research Allocation Committee (RAC)'''. | |
| − | + | '''Licensed software''' packages such as Fluent and Abaqus may be subject to additional limits. Such limits are presently suspended but may be re-instituted if the limit of available licenses is approached. | |
| + | |} | ||
Latest revision as of 14:19, 22 September 2016
Default Execution LimitsExecution limits at the Centre for Advanced Computing are in place to provide greater flexibility in scheduling user applications. The following table shows the default limits that are currently in place. Note that our clusters are undergoing extensions and re-structuring, and that these limits are likely to change in the near future. Please check sporadically to keep up-to-date with them.
Important Note: Research groups will in many cases require more resources, especially in terms of thread/process numbers, and may fall outside of these limits. We will work with these users to ensure appropriate access. Any requests for enhanced access should include specifications for number of processors required, total amount of memory, and the expected maximum runtime(s). Contact User Support to ensure that this is arranged using the most appropriate resource. Long-term extended usage requires a formal application to Compute Canada. Calls for such applications are currently issued once a year in the fall. We are announcing these calls on our web page. The allocation is done by a Research Allocation Committee (RAC). Licensed software packages such as Fluent and Abaqus may be subject to additional limits. Such limits are presently suspended but may be re-instituted if the limit of available licenses is approached. | ||||||||||||
