Difference between revisions of "Allocation"

From CAC Wiki
Jump to: navigation, search
(Comparison: Allocation on SW/CAC (SGE) vs Frontenac (SLURM))
(Comparison: Allocation on SW/CAC (SGE) vs Frontenac (SLURM))
Line 19: Line 19:
 
|-
 
|-
 
| Default allocation (compute)
 
| Default allocation (compute)
| 48 core limit
+
|  
| 50 core years over 1 year
+
* 48 core limit
 +
* excludes dedicated systems
 +
* job limits may apply
 +
|  
 +
* 50 core years over 1 year
 +
* default partition
 +
* no scheduling to "large nodes"
 +
* job limits may apply
 
|-
 
|-
 
| RAC allocation (compute)  
 
| RAC allocation (compute)  

Revision as of 16:29, 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.

Fair share vs core/job restrictions

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
  • excludes dedicated systems
  • job limits may apply
  • 50 core years over 1 year
  • default partition
  • no scheduling to "large nodes"
  • job limits may apply
RAC allocation (compute)
  • fixed core limit
  • according to allocation from Compute Canada
  • associated with dedicated node
  • scheduled to specific node by user
  • fixed core-years allocation over one year
  • allocation from Compute Canada (less than ask!)
  • scheduled to "reserved pool" at higher priority (5)
  • no dedicated resources
  • compete with other users of same priority
Allocation for "contributed" accounts (compute)
  • fixed core limit depending on size of contributed system
  • allocation from depends on system size
  • associated with dedicated node
  • scheduled to specific node by user
  • fixed core-years allocation over one year
  • allocation depends on system size
  • scheduled to "reserved" partition at very high priority (10)
  • no dedicated resources
  • compete with other users of same priority