Hi Thomas, On 6/15/26 11:06, Thomas Hartmann wrote:
if I get you right you want to have Condor effectively assign smaller CPU weights to a job than what the nominal single core to total core count would be, or?
yeah
Maybe going the other way could be easier? I.e., setting up more job slots than there are cores on a EP. (and scale up "proper" jobs up to the nominal single core/total core weight). Maybe something like preparing 10*#cores as slot count on a node and than quantize up such a "fractional slot" ð
Hmm, thus in the slot definition
NUM_SLOTS_TYPE_1 = 1
SLOT_TYPE_1 @=slot
cpus = 16
ram = 45%
swap = 0%
GPUS = auto : Regexp("0000:[04][89CD]:00.0", DevicePciBusId)
@slot
I would exchange `cpus = 16` by `cpus = 160` and maybe add something like
MODIFY_REQUEST_EXPR_REQUESTCPUS = quantize( RequestCpus * IfTheElse(
isUndefined(Target.TinyJob), 10.0, 1.0), {1})
?(no testing so far, I don't even know if I can perform maths there yet and whther I mix up 'My' and 'Target' again).
IOW, if a job has `+TinyJob = true` defined, `request_cpus = 1` would effectively only use a tenth of a core otherwise 10/10. Does that sound about right?
Cheers Carsten -- Dr. Carsten Aulbert, Max Planck Institute for Gravitational Physics, CallinstraÃe 38, 30167 Hannover, Germany, Phone +49 511 762 17185
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature