[GE users] maximum number of running jobs/tasks

Reuti reuti at staff.uni-marburg.de
Tue May 1 17:53:02 BST 2007


Am 27.04.2007 um 17:46 schrieb Heywood, Todd:

>> Am 27.04.2007 um 03:18 schrieb Heywood, Todd:
>>
>>> Is it possible for user-controlled limiting of the number of
>>> simultaneously running tasks of an array job? For example, a user
>>> may want to submit a 200 task job array, but have only the first
>>> 100 start running while the other stay in state "qw", with waiting
>>> tasks starting to run as running tasks finish.
>>>
>>> As of a year ago, it seems that a "per job" max_aj_instances was
>>> not possible:
>>>
>>> http://gridengine.sunsource.net/servlets/ReadMsg?
>>> list=users&msgNo=15890
>>>
>>> Nothing has changed since?
>>>
>>> The context here is that a large number of tasks can reduce the
>>> memory demands per task, but too many tasks running simultaneously
>>> hits NFS bottlenecks. Users would like to be able to control the
>>> tradeoff, which is application-specific.
>>
>> could you use a consumable complex for this?
>>
>
> What could a consumable complex do that setting aj_max_instances  
> wouldn't
> do? I don't understand how this would allow job and/or user level  
> control,
> rather than global configuration level (set by admin).

Yes, this was the idea. You would need of course one complex per job  
prepared by the admin.

-- Reuti

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list