Allocations and compute scheduling: Difference between revisions

''Parent page: [[Job scheduling policies]]''

'''An allocation is an amount of resources that a research group can target for use for a period of time, usually a year.''' This amount is either a maximum amount, as is the case for storage, or an average amount of usage over the period, as is the case for shared resources like computation cores.

[[File:Select view group usage edit.png|thumb|Navigation to ''View Group Usage'']]

Information on the usage of compute resources by your groups can be found by logging into the CCDB and navigating to ''My Account > View Group Usage''.

: '''By Compute Resource''': cluster on which jobs are submitted;  

: '''By Resource Allocation Project''': projects to which jobs are submitted;

: '''By Submitter''': user that submits the jobs;

: '''Storage usage''' is discussed in [[Storage and file management]].  

From the ''Extra Info'' column of the usage table ''Show monthly usage'' can be clicked to display a further breakdown of the usage by month for the specific cluster row in the table. By clicking ''Show submitter usage'', a similar breakdown is displayed for the specific users submitting the jobs on the cluster.

Nothing bad.  Your CPU or GPU allocation is a target level, i.e., a target number of CPUs or GPUs.  If you have jobs waiting to run, and competing demand is low enough, then the scheduler may allow more of your jobs to run than your target level.  The only consequence of this is that succeeding jobs of yours ''may'' have lower priority for a time while the scheduler prioritizes other groups which were below their target.  You are not prevented from submitting or running new jobs, and the time-average of your usage should still be close to your target, that is, your allocation.