 |
 |
Hi John R. Hover wrote: > 3) What are the units for the cycle_time config variable? And is this > referring to how frequently condor worker nodes ask for jobs, i.e. > NEGOTIATOR_INTERVAL? That does appear to be available from > condor_config_val. Cycle time is in seconds. If you're not sure what to set, set it as zero. This value is somewhat historical and the documentation on it could be better. It used to be (Torque v1) that Torque/Maui had the concept of a scheduling cycle; you set this, and every N seconds Maui would look at the pool of nodes, find free slots, and schedule them. This means that even for a free system, N/2 is the ERT ... you don't know where you will land in the scheduling cycle, so your best guess is "in the middle" so you will wait on average half a scheduling cycle before your job starts to run. More recent torque versions send "term" signals to Maui when a job occupying a run slot terminates, so scheduling is immediate, meaning there is not really a cycle, so the "scheduling cycle" is effectively zero seconds. If you have nodes asking for jobs asynchronously, an unbiased value would be NEGOTIATOR_INTERVAL / M where M is the number of worker nodes ... but again zero is probably a fine value unless NEGOTIATOR_INTERVAL is order minutes and you don't have very many nodes. JT