[gridengine users] squeezing in other jobs
mgstauff at gmail.com
Mon May 18 18:28:40 UTC 2015
A related solution to my original goal for anyone interested, is to submit
array jobs with the -tc option:
-allow users to limit concurrent array job task execution.
ning_tasks specifies maximum number of simultaneously
running tasks. For exam-
ple we have running SGE with 10 free slots. We call qsub -t
1-100 -tc 2 job-
script. Then only 2 tasks will be scheduled to run even when
8 slots are free.
On Mon, May 18, 2015 at 2:23 PM, Michael Stauffer <mgstauff at gmail.com>
> On Thu, May 14, 2015 at 4:31 PM, Reuti <reuti at staff.uni-marburg.de> wrote:
>> Am 14.05.2015 um 20:22 schrieb Michael Stauffer:
>> > OGS, via Rocks 6.1
>> > Hi,
>> > Sometimes users have jobs running that fill they're quota, and want to
>> suspend one of them in order to run a different immediate job, and then
>> continue the suspended job. I've experimented with suspending running jobs
>> and submitting a new job, but the new job doesn't run. Should it? Is there
>> a different way to do this?
>> How should SGE know which job to suspend to lower the quota temporarily?
>> There is no look-ahead feature in SGE to make such decisions. Once resource
>> are granted, they are used up also by suspended jobs.
> I was experimenting with suspending the jobs manually, so SGE wouldn't
> have to decide. But in any case, seems my goal isn't possible using
> suspension, thanks, so I'll stick with placing holds on queued jobs, and
> look into checkpointing.
>> -- Reuti
>> > Related to this, I've seen that if the user's quota is full and also
>> has a number of queued jobs, the queued jobs can have a hold placed on
>> them, and a newly submitted job will then run once one of the running jobs
>> has completed. This works for some cases, but if the running jobs are long,
>> it's less attractive.
>> > Thanks
>> > -M
>> > _______________________________________________
>> > users mailing list
>> > users at gridengine.org
>> > https://gridengine.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users