Re: [HTCondor-users] More thoughts on memory limits

[Jeff Templon <templon@xxxxxxxxx>]

Hi,

Thanks for this, as it was a big mystery to us - the memory values reported by HTCondorâs âhistoryâ command are now essentially useless, I guess this is why, you have to get âluckyâ for them to be meaningful.

Context: the typical use cases for looking at memory history are

 1) operational, why have machines been running low on memory?  The history will no longer give you hints.
 2) user-oriented: how much memory do my jobs use, so I know how much memory to specify in the JDL?  The history is no longer a reliable source of information.

Itâs almost as bad as picking some random moment in the life of the job for which the used CPU and Wall times will be reported for the job.  

> On 1 Dec 2024, at 12:24, Petr Vokac <petr.vokac@xxxxxxx> wrote:
> 
> btw: I find questionable to re-use existing cgroup slot from previous jobs with stuck processes for a new HTCondor job and I hope that developers comes with cleaner solution in future..

Yes, especially if it leads to poor accounting data.

JT