Re: [HTCondor-users] ResidentSetSize

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 5/10/2016 3:24 PM, Bob Ball wrote:
> > 2. Suggest using MemoryUsage for all policy expressions instead of
> > ResidentSetSize.
> MemoryUsage = ( ( ResidentSetSize + 1023 ) / 1024 )
>
> How will this help in this expression, other than just rounding 27GB a
> bit?
Besides using the same units as RequestMemory, MemoryUsage represents 
what the HTCondor developers think is currently the best representation 
available for a job's memory usage.  Once upon a time we recommended 
that everyone use ImageSize.  Then everyone changed all their 
expressions to use ProportionalSetSizeKb, then changed again to 
ResidentSetSize.  Instead of admins changing expressions as more subtle 
low-level metrics are introduced, the thinking is policy expressions 
could just use MemoryUsage.
> What happens with this expression at first, when ResidentSetSize
> is not yet available?
It will evaluate to UNDEFINED, same as ResidentSetSize.

regards
Todd