Am 24.06.2019 um 12:59 schrieb Semi <s...@bgu.ac.il>:
> Hi 
> I have a question, one of our users A. submit parallel jobs with 144 slots 
> wit high priority
> Other user B. submit a lot of single jobs with low priority.
> How can I define that job A will be executed before B?
> In this case there is no 144 free slots for now.
> I know that single job with low priority always will be executed before 
> parallel job,
> that will wait till 144 free slots.

Did you set up some slot reservation? I.e. submitting the large parallel jobs 
with `qsub -R y …` and enabling the reservation in SGE’s scheduler 

$ qconf -ssconf
max_reservation                   20
default_duration                  8760:00:00

Usually this should avoid job starvation, and reserve the slots for the 
parallel job. If a proper amount of wallclock time (h_rt) is specified for the 
small serial jobs, backfilling might apply (instead of slots being idle) and 
they may run although slots are reserved – but they are supposed to end before 
any of the already running jobs will end.

Note the "default_duration" was set to a real value. The default "infinity" 
would lead to the effect, that infinity is always judged of being smaller than 
infinity and (endless) backfilling will occur all of the time. Even already 
running jobs must get this values applied (h_rt), as they would otherwise keep 
the queue open for the small jobs. Or just wait until all running jobs without 
this constraint were drained.

-- Reuti
users mailing list

Reply via email to