Allocations and compute scheduling: Difference between revisions

Westgrid trng video unavailable, rm paragraph referring to it
No edit summary
(Westgrid trng video unavailable, rm paragraph referring to it)
Line 88: Line 88:
<!--T:13-->
<!--T:13-->
Another common case is when a job requests memory beyond what is associated with the cores requested. If a cluster that has 4GB of memory associated with each core receives a job request for only a single core but 8GB of memory, then the job will be deemed to have used two cores. This is because other researchers were effectively prevented from using the second core because there was no memory available for it.
Another common case is when a job requests memory beyond what is associated with the cores requested. If a cluster that has 4GB of memory associated with each core receives a job request for only a single core but 8GB of memory, then the job will be deemed to have used two cores. This is because other researchers were effectively prevented from using the second core because there was no memory available for it.
<!--T:14-->
The details of how resources are accounted for require a sound understanding of the core equivalent concept, which is discussed below.<ref>Further details about how priority is calculated are beyond the scope of this document. Additional documentation is in preparation. We also suggest that a [https://www.westgrid.ca/events/scheduling_job_management_how_get_most_cluster training course] might be valuable for anyone wishing to know more.</ref>


=What is a core equivalent and how is it used by the scheduler?= <!--T:15-->
=What is a core equivalent and how is it used by the scheduler?= <!--T:15-->
Bureaucrats, cc_docs_admin, cc_staff
2,879

edits