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

Re: [HTCondor-users] Are evicted jobs memory requirements automatically adjusted?

Are you sure about this?

When I submit a job with no "request_memory" statement it defaults to this _expression_:

RequestMemory = ifthenelse(MemoryUsage =!= undefined,MemoryUsage,( ImageSize + 1023 ) / 1024)

However, when I set "request_memory = 500" it is plain:

RequestMemory = 500

therefore discarding anything that condor might have learned about the actual memory requirements of the job. Wouldn't it be better that if "request_memory" is used this _expression_ would be set to:

RequestMemory = max(500,  ifthenelse(MemoryUsage =!= undefined,MemoryUsage,( ImageSize + 1023 ) / 1024))


On 6 February 2013 18:20, Ian Chesal <ian.chesal@xxxxxxxxx> wrote:
On Wed, Feb 6, 2013 at 6:48 AM, Chris Filo Gorgolewski <krzysztof.gorgolewski@xxxxxxxxx> wrote:
When a job gets suspended and evicted it's memory requirements adjusted by the actual values measured during it's execution?

For example:
1. I job with "request_memory = 500" is being submitted.
2. The job gets assigned to a node, starts running.
3. It allocates 2000MB.
4. The job gets suspended and evicted (reason does not really matter in this example)
5a. Job gets resubmitted to another node with memory requirement of 500MB (as requested by the user)
5b. Job gets resubmitted to another node with memory requirement of 2000MB (as measured during previous execution)

So which one is it 5a or 5b?

5b. Unless you do something specific to prevent it, but it doesn't sound like you are messing with the ImageSize _expression_ that gets generated when you use request_memory to set the memory expectation.

- Ian

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: