Hi all,is there a way to define a new dynamic slot, whose cpu weighting has a different weight than a parallel standard dynamic slot? I.e., a dedicated slot whose dynamic sub-slots have a minimal cpu share - so one can run low prio background jobs on these for jumping on free cycles?
In cgroups v1 the idea would aim to something in the direction like [1].With cgroups v2 it might be similar, but I am not yet as firm with v2 yet...
Is this possible? (avoiding trying to set up a second low-prio startd with a dedicated cgroup base dir with weights - in parallel to a vanilla startd)
Cheers, Thomas [1] [normal slots] condor_var_lib_condor_execute_slot1_1@xxxxxxxx/cpu.shares 100 condor_var_lib_condor_execute_slot1_2@xxxxxxxx/cpu.shares 800 [low weight slots] condor_var_lib_condor_execute_slot2_1@xxxxxxxx/cpu.shares 5 condor_var_lib_condor_execute_slot2_2@xxxxxxxx/cpu.shares 5 or ideally a sub-sub-group? slot2@xxxxxxxx/cpu.shares [10] slot2@xxxxxxxx/slot2_1/cpu.shares [100] slot2@xxxxxxxx/slot2_2/cpu.shares [100]
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature