[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] slight bug in dynamic slots

Yes that worked.

The default value should be zero if dynamic slots are in use (if

On Mon, May 16, 2011 at 10:48 AM, Lukas Slebodnik <slebodnik@xxxxxxxx> wrote:
> Hi Erik,
> You can change tihs behaviour by setting variable CLAIM_WORKLIFE.
> http://www.cs.wisc.edu/condor/manual/v7.4/3_3Configuration.html#16308
> This variable specifies the number of seconds after which a claim will stop
> accepting additional jobs.
> Regards,
> Lukas
> On Mon, May 16, 2011 at 10:35:40AM -0400, Erik Aronesty wrote:
>> When a job on a dynamic slot (slot1.1 for example) completes, the
>> dynamic slot is marked as "available/unclaimed" for a brief window of
>> time before it is reaped and the resources it consumes are made
>> available to the primary slot (slot1).
>> During that time a job can be scheduled on it.... a job with far less
>> RAM or #CPUS than the slot has reserved.
>> This results in a large inefficiency in job allocation when the queue
>> is very busy, and there are lots of mixed jobs... some reserving high
>> numbers of cpus and  others reserving few.
>> - ERik
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/