![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||
By default, the grid engine system schedules job runs in a fixed schedule interval. You can use the Flush Submit Seconds and Flush Finish Seconds parameters to configure immediate scheduling. For more information, see Immediate Scheduling. To change load adjustment parameters, click the Load Adjustment tab. The Load Adjustment tab looks like the following figure: ![]() Use the Load Adjustment tab to set the following parameters:
See Scaling System Load for background information. See the sched_conf(5) man page for more details about the scheduler configuration. Administering PoliciesThis section describes how to configure policies to manage cluster resources. The grid engine software orchestrates the delivery of computational power, based on enterprise resource policies that the administrator manages. The system uses these policies to examine available computer resources in the grid. The system gathers these resources, and then it allocates and delivers them automatically, in a way that optimizes usage across the grid. To enable cooperation in the grid, project owners must do the following:
As administrator, you can define high-level usage policies that are customized for your site. Four such policies are available:
Policy management automatically controls the use of shared resources in the cluster to achieve your goals. High-priority jobs are dispatched preferentially. These jobs receive greater CPU entitlements when they are competing with other, lower-priority jobs. The grid engine software monitors the progress of all jobs. It adjusts their relative priorities correspondingly, and with respect to the goals that you define in the policies. This policy-based resource allocation grants each user, team, department, and all projects an allocated share of system resources. This allocation of resources extends over a specified period of time, such as a week, a month, or a quarter. Configuring Policy-Based Resource Management With QMONOn the QMON Main Control window, click the Policy Configuration button. The Policy Configuration dialog box appears. Figure 5-1 Policy Configuration Dialog Box ![]() The Policy Configuration dialog box shows the following information:
From this dialog box you can access specific configuration dialog boxes for the three ticket-based policies. Specifying Policy PriorityBefore the grid engine system dispatches jobs, the jobs are brought into priority order, highest priority first. Without any administrator influence, the order is first-in-first-out (FIFO). On the Policy Configuration dialog box, under Policy Importance Factor, you can specify the relative importance of the three priority types that control the sorting order of jobs:
For more information about job priorities, see Job Sorting. You can specify a weighting factor for each priority type. This weighting factor determines the degree to which each type of priority affects overall job priority. To make it easier to control the range of values for each priority type, normalized values are used instead of the raw ticket values, urgency values, and POSIX priority values. The following formula expresses how a job's priority values are determined:
Urgency, Ticket, and Priority are the three weighting factors you specify under Policy Importance Factor. For example, if you specify Priority as 1, Urgency as 0.1, and Ticket as 0.01, job priority that is specified by the qsub -p command is given the most weight, job priority that is specified by the Urgency Policy is considered next, and job priority that is specified by the Ticket Policy is given the least weight. Configuring the Urgency PolicyThe Urgency Policy defines an urgency value for each job. This urgency value is determined by the sum of the following three contributing elements:
For details about how the grid engine system arrives at the urgency value total, see About the Urgency Policy. | ||
| ||
![]() |