Allocations and compute scheduling: Difference between revisions

Line 29: Line 29:


[[File:Ccdb view use by compute resource.png|thumb|View of group usage by compute resource.]]
[[File:Ccdb view use by compute resource.png|thumb|View of group usage by compute resource.]]
Using the top selection bar 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 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.
[[File:Ccdb view use by compute resource monthly.png|thumb|Usage by compute resource with monthly breakdown.]]


== What happens if my group overuses my CPU or GPU allocation? == <!--T:32-->
== What happens if my group overuses my CPU or GPU allocation? == <!--T:32-->
cc_staff
55

edits