[torqueusers] scheduling cycle
anwar at cse.unl.edu
Thu Aug 2 21:43:42 MDT 2007
So there is no job start or job finish trigger. Scheduler tries to schedule
in each scheduling cycle. Am I right?
Then how do we decide the scheduling interval?
From: David Singleton [mailto:David.Singleton at anu.edu.au]
Sent: Thursday, August 02, 2007 9:09 PM
To: Ai Niwaer; torqueusers at supercluster.org
Subject: Re: [torqueusers] scheduling cycle
Some other cases that require scheduling cycles include:
- if a job finishes while the scheduler is actually making scheduling
decisions, it is not informed that there are more resources free. If
no other jobs are queued or terminate for some time, those resources
will remain unutilised.
- reordering the queued jobs and resetting priorities based on time in
queued state etc
- pre-emption/suspension/resumption sceduling might happen when some time
dependent threshold is reached but no job state changes
- the scheduler might employ day/night peak/offpeak configurations that
the server is unaware of.
Garrick Staples wrote:
> On Thu, Aug 02, 2007 at 11:56:19AM -0500, Ai Niwaer alleged:
>> What is scheduling cycle? If server trigs when a new jobs come or a jobs
>> finishes, why do we still need scheduling cycle?
> Because other factors can influence scheduling, such as nodes becoming
> time-based reservations, etc.
More information about the torqueusers