Re: [HTCondor-users] min memory without request_memory defined

[Vikrant Aggarwal <ervikrant06@xxxxxxxxx>]

Thain mentioned method is definitely a recommended one.Â

I recently found Job Transform mentioned in slide 11 (and some others) very useful for adding something to job classad depending upon the conditions.Â

https://research.cs.wisc.edu/htcondor/HTCondorWeek2017/presentations/TueKnoeller_Schedd.pdf

Thanks & Regards,

Vikrant Aggarwal

On Fri, Jun 7, 2019 at 8:11 PM Michael Di Domenico <mdidomenico4@xxxxxxxxx> wrote:

i want to assign a minimum amount of memory that all jobs get when no
requestmemory classad is added to the submit file.

by default i see the classad gets set to

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

after the job starts, but in my case, the job is sort lived and
Imagesize gets set to 1. therefore if a job (python script in this
case) uses more then 1MB of memory it gets put on hold.

I'd like to set it so the starting Request_Memory variable if it's
undefined is 1GB. Ideally it would also be nice if i could ensure
that no job is submitted with less the 1GB specified. yes, yes, i
know it's wasteful, but we have way more memory then slots on our
nodes and most people seem to use less then 1GB anyhow, so it
balances...

i have
modify_request_expr_requestmemory = quantize(requestmemory,{1024})

but i don't think it's doing what i think it's doing. i can't recall
where i got that stanza from
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/