Difference between revisions of "Allocation"
(→Comparison: Allocation on SW/CAC (SGE) vs Frontenac (SLURM)) |
(→Comparison: Allocation on SW/CAC (SGE) vs Frontenac (SLURM)) |
||
| Line 43: | Line 43: | ||
| | | | ||
* fixed core-years allocation over one year | * fixed core-years allocation over one year | ||
| − | * allocation depends on | + | * allocation depends on system size |
| − | * scheduled to "reserved | + | * scheduled to "reserved" partition at very high priority (10) |
* no dedicated resources | * no dedicated resources | ||
* compete with other users of same priority | * compete with other users of same priority | ||
|} | |} | ||
Revision as of 16:26, 8 February 2018
Resource Allocations on the Frontenac Cluster
This Wiki entry is meant to explain how resources are shared on the CAC Frontenac cluster. This includes default allocations in terms of Compute time as well as extended resources that were allocated by Compute Canada or that come from contributed systems. We also point out differences between the current Frontenac allocation scheme and the older scheme that was used on the now decommissioned SW/CAC clusters.
Our job scheduler on Frontenac is [SLURM https://slurm.schedmd.com/]. All resource allocations and limitations are applied through this scheduler. For a basic intro on how to use it, please see our scheduler help file.
Every user on our systems has at least one SLURM account, the default account. Users with access to extended resources have additional accounts corresponding to these allocations. These SLURM accounts have intrinsic restrictions and allow scheduling of jobs up to these limits.
Comparison: Allocation on SW/CAC (SGE) vs Frontenac (SLURM)
| Allocation Feature | SW/CAC (SGE) | Frontenac (SLURM) |
| Default allocation (compute) | 48 core limit | 50 core years over 1 year |
| RAC allocation (compute) |
|
|
| Allocation for "contributed" accounts (compute) |
|
|
