MAUI TORQUE Torque Job manager Accept and dispatch

MAUI / TORQUE Torque : Job manager Accept and dispatch the job Provide the job status on batch system Maui: Make the decision concerning job execution. Work by iteration or on demand ( end of job, new job incoming). Torque is a « black box » to push the job, and Maui is the brain who decide what job have to be push first.

MAUI JOB STATUS AND PRIORITY Three levels of job status are available from MAUI • Active: Job are running • Idle: Priority of the job is calculated from the scheduling rules but the job is not running. Idle job list is a view of the job already scheduled. • Blocked : Scheduling rules are not apply to the job because a hard rules is apply on this job. Job priority is define from 6 components • Credential, Fairshare, Resources, Services, Target, Usage • Priority = Credential + Faishare +Resources +…. .

MAUI PRIORITY Credential Priority = CREDWEIGHT * ( USERWEIGHT *Priority. U + GROUPWEIGHT *Priority. G + ACCOUNTWEIGHT*Priority. A + QOSWEIGHT*Priority. Q + CLASSWEIGHT*Priority. C) Resource Priority = RESWEIGHT * ( NODEWEIGHT *Total. Nodes. Req + proc, mem, swap, disk, … Service A set of subcomponent to specifies which services metrics are greatest value QUEUETIME : FIFO order priority XFACTOR : Increase the short jobs priority ……

MAUI PRIORITY Fairshare Priority = FSWEIGHT * ( FSUSERWEIGHT *Delta. U + FSGROUPWEIGHT *Delta. G + FSACCOUNTWEIGHT*Delat. A + FSQOSWEIGHT*Delta. Q + FSCLASSWEIGHT*Delta. C) Delta. X = Fairshare target – Fairshare usage or 1 – (Fairshare usage/ Fairshare target) ( depending of FSPOLICY value) Fairshare usage define from « processor dedicated » or « processor consumed » depending of the FSPOLICY value Fairshare usage are based on historical usage • FSINTERVAL duration of each fairshare window • FSDEPTH number of fairshare windows factored into current fairshare utilization • FSDECAY decay factor applied to weighting the contribution of each fairshare window

MAUI PRIORITY Use a limited number of component ( credentiel and/or fairshare should be enough). Try to use a minimal set of element ( user, group, class, …) to build priority rules. Have a look to be sure that no one jobs fall on a « black hole » . Have a look to be sure that the reality of the scheduling is close to expected scheduling ( Maui now can run on simulate mode). Example : fairshare of 80% for ATLAS production job.