Allocations and compute scheduling: Difference between revisions

It should be noted that in the case of core year and GPU year allocations, both of which target resource usage averages over time on shared resources, a research group is more likely to hit (or exceed) its target(s) if the resources are used evenly over the allocation period than if the resources are used in bursts or if use is put off until later in the allocation period.

[[File:Select view group usage edit.png|thumb|Navigation to "View Group Usage" at the Compute Canada portal. ]]

Summaries of account usage can be explored by logging into ccdb.computecanada.ca and navigating to ‘My Account’ > ‘View Group Usage’. CPU and GPU core year values are calculated based on the quantity of the resources allocated to jobs on the clusters. It is important to note that the values summarized at the View Group Usage pages do not represent core-equivalent measures such that, in the case of large memory jobs, the usage values will not match the cluster scheduler’s representation of the account usage. <br clear=all>

[[File:Ccdb view use by compute resource.png|thumb|View of group usage by compute resource.]]

The initial view of the usage at the View Group Usage page is divided up ‘By Compute Resources” (specific compute clusters, e.g. Beluga, Cedar, etc) which summarizes together the usage of all groups that the logged in user either owns or belongs to. The initial view begins with the current allocation year (starting on April 1st) up to the current date. <br clear=all>

[[File:Ccdb view use by compute resource monthly.png|thumb|Usage by compute resource with monthly breakdown.]]

Using the top selection bar of the View Group Usage page compute usage summaries can be grouped “By Compute Resources” (specific compute clusters, e.g. Beluga, Cedar, etc), “By Resource Allocation Project” (corresponding to the group account that jobs are submitted to, e.g. def-*, rrg-*, etc.), or “By Submitter” (corresponding to the specific users that submitted the jobs). The top selection bar also provides an option to display “Storage Usage”.

The table summaries for the current year provide a row for each compute resource (cluster), the “Total CPU Usage (in core years)” to date as well as the “Projected CPU Usage (in core years)” which assumes that the throughput achieved to date will be maintained for the remainder of the allocation period.

The “Year:” selection bar in the top panel of the View Group Usage page provides archival summaries of “Total CPU Usage (in core years)” for previous allocation years for which the “Projected CPU Usage” column is eliminated.

The “Extra Info” columns of the summary tables provide further breakdowns by “monthly” or “submitter” usage respectively. <br clear=all>

[[File:Ccdb view use by compute resource monthly proj edit.png|thumb|Usage by Resource Allocation Project with monthly breakdown.]]

The scheduling software implements the fair share usage policy across all Resource Allocation Projects (group accounts) on the specific cluster. Selecting the “By Resource Allocation Project” displays the summaries of specific project allocations and their usage on the clusters. This will display a new selection bar at the top of the View Group Usage page listing the available RAPIs (Resource Allocation Project Identifiers) for the selected allocation year. Selecting a specific RAPI displays various summary fields including the account name (e.g. def-*, rrg-* or rpp-*, etc), the project name and ownership as well as allocation and usage summaries. A single Resource Allocation Project may have allocations and usage on several clusters. This view divides the project’s allocations and usage uniquely across the clusters. The summary for the current allocation year provides columns for the “Resource” containing the allocation, “Allocations” details, “Total Core-Years Allocated”, “Total CPU Usage (in core years)”, “Utilization” expressed as a percentage of the allocation used, “Projected CPU Usage (in core years)” and “Projected Utilization” expressed as a percentage of the allocation projected use. <br clear=all>