[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] request_memory
- Date: Thu, 2 Jan 2014 12:07:51 -0500 (EST)
- From: Tim St Clair <tstclair@xxxxxxxxxx>
- Subject: Re: [HTCondor-users] request_memory
Just a nit, but neither this thread or the wiki references :
Which is likely useful for the original request:
"I have a job with request_memory = 256 Megabytes but if I go over it will get held according to my SYSTEM_PERIODIC_HOLD policy. I would like to automatically triple the request_memory and then release the job. Is that possible to do?"
----- Original Message -----
> From: "Todd Tannenbaum" <tannenba@xxxxxxxxxxx>
> To: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
> Sent: Thursday, January 2, 2014 10:33:18 AM
> Subject: Re: [HTCondor-users] request_memory
> On 1/2/2014 8:12 AM, Brian Bockelman wrote:
> > Boo! Hiss! ImageSize is bad!
> Ideally, folks want to know how much physical RAM a given job is using.
> ImageSize, which is a sum of the virtual address space used by all
> processes in the job, is not ideal because it often much larger than
> the amount of physical ram in use. The only advantage of ImageSize is
> it exists on all platforms and in all versions of HTCondor.
> For HTCondor v8.0+, consider using MemoryUsage instead. MemoryUsage is
> the peak physical memory usage for the job in megabytes, or as best an
> estimate as HTCondor can do on a given operating system. Perfect. Be
> aware that MemoryUsage is not defined until the job actually runs.
> There are many other "lower level" attributes that characterize the
> memory usage of an application, such as ResidentSetSize,
> ProportionalSetSizeKb, etc. But unless you have something very specific
> in mind, MemoryUsage is what you want.
> ps - For more wisdom/recipes related to memory usage, see
> 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: