Il 06.05.2014 19:02, Skylar Thompson ha scritto:
I think weight_waiting_time in sched_conf(5) is the attribute you'll want
to tune.
humm.. I guess that is taken into account only when the resources are
available and more than one large parallel jobs are pending in the
queue.. right? I mean, that alone will not solve the starving problem of
the large parallel jobs..
Thank you and best regards.
Robi
On Tue, May 06, 2014 at 06:45:23PM +0200, Roberto Nunnari wrote:
Hello.
I'm running a small cluster using Oracle Grid Engine 6.2u7
At times it happens that one user submits a job that requires several
resources (-pe, -l mem_free, etc).
For instance, user A submits a job X requiring 32 slots out of 100
available.
The other users, keeps submitting serial jobs filling up all the slots
and always having more jobs waiting on the queue.
The serial jobs will get ahead of job X, and be scheduled as soon as one
slot is available and job X will be waiting in the queue forever and
never get to run until no more serial jobs will be submitted and 32
slots will be available.
I would like the scheduler to also consider how much the job has been
waiting in the queue, and possibly also the values regarding the
historic users resources usage, as returned by qacct -o username
What are the possible solutions to solve this problem?
Thank you and best regards.
Robi
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
