[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[HTCondor-users] CPU share handling changed with 8.6.5-1?



Hi all,

after updating to ~8.6.5 it seems that the scaling fractions for the CPU
share cgroup has changed.

So far I had assumed the CPU share to be requested CPU x 100 for the
jobs' child groups with the condor parent share normally equivalent to
the global share.
Now the basic scaling factor within the child cgroups seems to be 1024, or?

Might also be a local problem at us - as also explicit 8core jobs now
end up with the same CPU share of 1024 as single core jobs but not 8192 [1]?


Cheers,
  Thomas


[1]
 353503 ?        Ss     0:00      \_ condor_starter -f -a slot1_3
grid-arcce0.desy.de
 369890 ?        S      0:00      |                           \_
condor_starter -f -a slot1_1 vocms0250.cern.ch
 370188 ?        S      0:00      |                           \_
condor_starter -f -a slot1_2 vocms0250.cern.ch
 371000 ?        S      0:00      |                           \_
condor_starter -f -a slot1_3 vocms0250.cern.ch
 371002 ?        S      0:00      |                           \_
condor_starter -f -a slot1_4 vocms0250.cern.ch
 371135 ?        S      0:00      |                           \_
condor_starter -f -a slot1_7 vocms0250.cern.ch
 371137 ?        S      0:00      |                           \_
condor_starter -f -a slot1_8 vocms0250.cern.ch
 371138 ?        S      0:00      |                           \_
condor_starter -f -a slot1_5 vocms0250.cern.ch
 371139 ?        S      0:00      |                           \_
condor_starter -f -a slot1_6 vocms0250.cern.ch

> cat
/cgroup/cpu/htcondor/condor_var_lib_condor_execute_slot1_3\@batch0930.desy.de/cpu.shares

1024

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature