[gridengine users] Priority?

Kandalaft, Iyad (AAFC/AAC) iyad.kandalaft at canada.ca
Thu Mar 7 17:07:08 UTC 2019


Your priority weight is set to 0.  Hence, submit a job with a -p will do nothing because the weight * the normalized priority will always equal 0.

Change
weight_priority                   0.000000
to a higher value
weight_priority                   0.500000

0.5 would make it equal to your weight_urgency.  In effect, the time the job has been waiting in the queue is as important as the priority assigned to the job.

Reducing weight_urgency and increasing weight_priority would reduce the impact of how long a job has been in the queue in the scheduling and increase the impact of -p.  


Cheers,
Iyad Kandalaft

Team Lead – Systems Development in Biological Informatics, ISB
Agriculture and Agri-Food Canada / Government of Canada
E-mail Address: iyad.kandalaft at canada.ca / Tel: 613-759-1228 / TTY: 613-773-2600

Chef d’equipe – Development des systemes dans l’informatique biologique, DGSI
Agriculture et Agroalimentaire Canada / Gouvernement du Canada
Adresse de courriel: iyad.kandalaft at canada.ca / Tél. : 613-759-1228 / ATS : 613-773-2600
 


-----Original Message-----
From: Simon Matthews <simon.d.matthews at gmail.com> 
Sent: Thursday, March 7, 2019 11:21 AM
To: Kandalaft, Iyad (AAFC/AAC) <iyad.kandalaft at canada.ca>
Cc: users Users <users at gridengine.org>
Subject: Re: [gridengine users] Priority?

On Thu, Mar 7, 2019 at 5:31 AM Kandalaft, Iyad (AAFC/AAC) <iyad.kandalaft at canada.ca> wrote:
>
> Hi Simon,
>
> Can you provide your scheduler config:
> $ qconf -ssconf
>
$  qconf -ssconf
algorithm                         default
schedule_interval                 0:0:15
maxujobs                          0
queue_sort_method                 load
job_load_adjustments              np_load_avg=0.50
load_adjustment_decay_time        0:7:30
load_formula                      np_load_avg
schedd_job_info                   true
flush_submit_sec                  0
flush_finish_sec                  0
params                            none
reprioritize_interval             0:0:0
halftime                          168
usage_weight_list                 cpu=1.000000,mem=0.000000,io=0.000000
compensation_factor               5.000000
weight_user                       0.250000
weight_project                    0.250000
weight_department                 0.250000
weight_job                        0.250000
weight_tickets_functional         0
weight_tickets_share              0
share_override_tickets            TRUE
share_functional_shares           TRUE
max_functional_jobs_to_schedule   200
report_pjob_tickets               TRUE
max_pending_tasks_per_job         50
halflife_decay_list               none
policy_hierarchy                  OFS
weight_ticket                     0.500000
weight_waiting_time               0.278000
weight_deadline                   3600000.000000
weight_urgency                    0.500000
weight_priority                   0.000000
max_reservation                   0
default_duration                  INFINITY


> It might explain the behavior you're seeing.
>
> As an aside, see man sge_priority(5) for an explanation of the scheduling.
>
> Iyad Kandalaft
>
> -----Original Message-----
> From: Simon Matthews <simon.d.matthews at gmail.com>
> Sent: Thursday, March 7, 2019 1:09 AM
> To: users Users <users at gridengine.org>
> Subject: [gridengine users] Priority?
>
> I have a small grid running SoGE 8.1.8,
>
> Prioritization doesn't seem to work. Jobs seem to run purely in the order they are submitted (after allowing for prerequisite jobs).
> Changing priority of the jobs doesn't seem to change the order in which they run.
>
> Can anyone else confirm this behaviour? Is there anything I might be doing wrong.
>
> Simon
>



More information about the users mailing list