Allocations and compute scheduling: Difference between revisions

Jump to navigation Jump to search
remove mention of unannounced system
m (Rdickson moved page Scheduling resources and allocations to Allocations and resource scheduling without leaving a redirect: Part of translatable page "Scheduling resources and allocations")
(remove mention of unannounced system)
Line 47: Line 47:


<!--T:17-->
<!--T:17-->
[[File:Core_equivalent_diagram_GP.png|frame|Figure 1 - Core equivalent diagram for Cedar, Graham, and Béluga.]]
[[File:Core_equivalent_diagram_GP.png|frame|Figure 1 - Core equivalent diagram for Cedar and Graham.]]


<!--T:18-->
<!--T:18-->
Cedar, Graham and Béluga are considered to provide 4GB per core, since this corresponds to the most common node type in those clusters, making a core equivalent on these systems a core-memory bundle of 4GB per core. Niagara is considered to provide 4.8GB of memory per core, make a core equivalent on it a core-memory bundle of 4.8GB per core. Jobs are charged in terms of core equivalent usage at the rate of 4 or 4.8 GB per core, as explained above.  See Figure 1.
Cedar and Graham are considered to provide 4GB per core, since this corresponds to the most common node type in those clusters, making a core equivalent on these systems a core-memory bundle of 4GB per core. Niagara is considered to provide 4.8GB of memory per core, make a core equivalent on it a core-memory bundle of 4.8GB per core. Jobs are charged in terms of core equivalent usage at the rate of 4 or 4.8 GB per core, as explained above.  See Figure 1.


<!--T:19-->
<!--T:19-->
Bureaucrats, cc_docs_admin, cc_staff
2,879

edits

Navigation menu