Il 12.11.2014 14:51, William Hay ha scritto:
On Wed, 12 Nov 2014 13:42:32 +0000
Roberto Nunnari <roberto.nunn...@supsi.ch> wrote:
Il 12.11.2014 14:33, William Hay ha scritto:
On Wed, 12 Nov 2014 13:14:25 +0000
Roberto Nunnari <roberto.nunn...@supsi.ch> wrote:
humm.. answering myself..
from the man pages it seams that
maxujobs is for only running jobs per user
while
max_u_jobs is for both running and pending jobs per user
is that correct?
Thank you and best regards
Robi
More or less. There is one other slight difference when it comes to array jobs.
Maxujobs counts each running task while max_u_jobs considers the whole array to
be a single job.
hehehe.. I still have to understand what a array job is.. and I don't
believe any of my users have ever used it. I'll try to find some doc
about it. :-)
It's a way to submit a bunch of jobs that are identical from grid engine's POV
as a single job. This lightens the load on the scheduler
and means qstat normally only reports a single queued job. Probably what the
user who caused your original issue should have submitted.
Nice! :-)
And the tasks in the array jobs can get running in parallel or they
always run in serial?
Robi
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
