Job priority is one factor that determines how iHub processes jobs. The administrator can set the maximum job priority for each user. If a user selects a job priority that is higher than this maximum, iHub runs the job at the assigned maximum priority level.

A user submitting a job request can also affect when a job executes by specifying a resource group. A resource group is a reserved set of Factory processes in an iHub instance. The administrator can set minimum and maximum priority levels for an asynchronous resource group to expedite job scheduling.

A job having an assigned resource group has priority over a job having no assigned resource group. When two jobs have the same priority, if one job has a resource group assignment and the other does not, the job with the resource group assignment executes first.

If you do not assign a resource group to a job, depending on the type of design the job runs, iHub assigns the job one of the following default resource groups:

The administrator can create any number of resource groups to run a particular design type. When you schedule a job to run a design, you select from the resource groups available to run that design type in Resource Group on Schedule—Schedule, as shown in Figure 5‑8.

If a user submits a scheduled job without assigning the job a resource group, and the priority level the user selects for the job is outside the range the default resource group assigned to the job specifies, the job is pending until the administrator changes the default resource group priority range to include the job priority level.