[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] slight bug in dynamic slots
- Date: Mon, 16 May 2011 16:48:59 +0200
- From: Lukas Slebodnik <slebodnik@xxxxxxxx>
- Subject: Re: [Condor-users] slight bug in dynamic slots
You can change tihs behaviour by setting variable CLAIM_WORKLIFE.
This variable specifies the number of seconds after which a claim will stop
accepting additional jobs.
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