[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] ImageSize value
- Date: Tue, 30 Jul 2019 16:04:10 +0000
- From: John M Knoeller <johnkn@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] ImageSize value
What you should be looking at is MemoryUsage rather than Image size.
condor_status normally will show only ImageSize, not ImageSize_RAW.
condor_q should have both an ImageSize and ImageSize_RAW value, ImageSize_RAW is the unquantized value, while
ImageSize is quantized from ImageSize_RAW. The quantization is meant to make matchmaking more efficient if the job
exits and needs to be re-run.
Detected values like MemoryUsage and ImageSize are updated periodically, and are not passed between daemons instantaneously,
So you should expect the values between condor_ q and condor_status to be a little bit different most of the time
because they represent the value of ImageSize at different times.
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Mathieu Bahin
Sent: Tuesday, July 30, 2019 9:53 AM
Subject: [HTCondor-users] ImageSize value
I'm developing an interface to monitor cluster jobs in my Institute.
We have the version 8.6.3 of Condo with partitionable slots.
I had the surprise to discover that the ImageSize value is different
whether I get it from "condor_status -l" or "condor_q -l" for the same
slot/job. Is there an explanation for that?
For example, I have, for the same job:
Â - from condor_q: ImageSize = 931876
Â - from condor_status: ImageSize_RAW = 1161832
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: