AW: AW: [GE users] Scheduling
andy.schwierskott at sun.com
Mon Sep 29 12:28:11 EDT 2003
job_load_adjustments are applied after a job has been dispatched.
So the first job should go into the queue, but not a seconds one immediately
>From SGE 5.3p3 you see SGE's internal bookkepping when a queue is in
(virtual) alarm state with
# qstat -j
It shows the real load and the job_load_adjustments what the scheduler used
in the last scheduling run.
On Mon, 29 Sep 2003, Olesen, Mark wrote:
> More scheduling woes ...
> I am now completely confused about how the scheduler is supposed to work.
> In accordance with sched_conf(5), I had assumed that the queues'
> "load_thresholds" would be considered during scheduling, but I'm seeing
> *somewhat* different behaviour.
> For all my queues, I've set
> load_thresholds np_load_avg=1.2
> As previously mentioned, I am sorting by seqno:
> algorithm default
> schedule_interval 0:0:15
> maxujobs 0
> queue_sort_method seqno
> user_sort true
> job_load_adjustments np_load_avg=0.5
> load_adjustment_decay_time 0:7:30
> load_formula np_load_avg
> schedd_job_info true
> The next queue in the sequence with any free slots has load_avg=2.05, or
> I would imagine that the scheduler predicts a new np_load_avg=1.53 (current
> + joad_load_adjustments). Since this predicted load is above the queue load
> threshold, I would not expect a new job to start on this queue.
> Contrary to my expectations, a new job does indeed get sent to this queue.
> What other tricks do I need in order to coerce the scheduler to respect the
> load thresholds?
> Dr. Mark Olesen
> Thermofluid Dynamics Analyst
> ArvinMeritor Light Vehicle Systems
> Zeuna Staerker GmbH & Co. KG
> Biberbachstr. 9
> D-86154 Augsburg, GERMANY
> tel: +49 (821) 4103 - 862
> fax: +49 (821) 4103 - 7862
> Mark.Olesen at ArvinMeritor.com
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net
More information about the Beowulf