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

Re: [HTCondor-users] 8.2.1 COUNT_HYPERTHREAD_CPUS still works?



yep.  flag_ht should be set.  Looks like a bug that we introduced in 8.1.x
it will be fixed in 8.2.2

On 7/9/2014 10:33 PM, Klint Gore wrote:

With STARTD_DEBUG=D_ALL,D_FULLDEBUG, the log says:

 

07/10/14 12:09:18 (fd:4) (pid:3936) (D_LOAD) Reading from /proc/cpuinfo

07/10/14 12:09:18 (fd:4) (pid:3936) (D_LOAD) Found: Physical-IDs:True; Core-IDs:True

07/10/14 12:09:18 (fd:4) (pid:3936) (D_ALWAYS:2) Using processor count: 12 processors, 12 CPUs, 0 HTs

 

The detected values are:

 

[root@agbu-cluster-01 condor]# condor_config_val -dump DETECTED*

# Configuration from machine: 10-1-1-101.agbu.localdomain

 

# Parameters with names that match DETECTED*:

DETECTED_CORES = 12

DETECTED_CPUS = 12

DETECTED_MEMORY = 64379

DETECTED_PHYSICAL_CPUS = 12

# Contributing configuration file(s):

#       /etc/condor/condor_config

#       /etc/condor/condor_config.local

 

 

From what I can see in ncpus.cpp, cpuinf->flag_ht must not be true otherwise it would have invoked linux_count_cpus_id.

 

Since its reading from cpuinfo the flags are

flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid

 

which has “ht” in it.

 

Klint.

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of John (TJ) Knoeller
Sent: Wednesday, 9 July 2014 1:16 PM
To: HTCondor-Users Mail List
Subject: Re: [HTCondor-users] 8.2.1 COUNT_HYPERTHREAD_CPUS still works?

 

There have been some changes to how this works in 8.2, but COUNT_HYPERTHREAD_CPUS should still impact the calculation of NUM_CPUS if you don't set
NUM_CPUS explicitly.

We recognised that the startd was picking an effective value for NUM_CPUS if you didn't set it.  And that calculation pays attention to COUNT_HYPERTHREAD_CPUS,
but in 8.0.x  the value of NUM_CPUS was never being set.  So you couldn't refer to it in your config files.

In 8.2 there are three automatic configuration variables that are set to remedy this.

DETECTED_PHYSICAL_CPUS  is set to the detected value of real CPUs it does not count hyperthreads
DETECTED_CORES                   is set to the detected value of hyperthreads.
DETECTED_CPUS                    is set to either the same value as DETECTED_CORES or as DETECTED_PHYSICAL_CPUS depending on what COUNT_HYPERTHREAD_CPUS is set to.
NUM_CPUS defaults to $(DETECTED_CPUS)

For example, here's the dump from my desktop.  (irrelevant lines omitted)

>condor_config_val -dump cpus cores
# Parameters with names that match cpus:
COUNT_HYPERTHREAD_CPUS = true
DETECTED_CPUS = 4
DETECTED_PHYSICAL_CPUS = 2
NUM_CPUS = $(DETECTED_CPUS)

# Parameters with names that match cores:
DETECTED_CORES = 4

Now the same command with COUNT_HYPERTHREAD_CPUS = false

# Parameters with names that match cpus:
COUNT_HYPERTHREAD_CPUS = false
DETECTED_CPUS = 2
DETECTED_PHYSICAL_CPUS = 2
NUM_CPUS = $(DETECTED_CPUS)

# Parameters with names that match cores:
DETECTED_CORES = 4

If DETECTED_PHYSICAL_CPUS is showing 12 then the problem isn't COUNT_HYPERTHREAD_CPUS, the problem is the detection code.

On 7/8/2014 2:13 AM, Klint Gore wrote:

Hi All,

 

Can anyone tell me if startd parameter COUNT_HYPERTHREAD_CPUS still works?  In my 8.0.6 setup, I had it on some 6 core i7’s and I only got 6 slots.  Now on 8.2.1 with the same setting, they get 12 slots.

 

The setting is in condor_config.local which according to MasterLog was read.

 

Centos 6.3, condor rpm from wisc.edu yum repository.

 

Thanks,

 

Klint.

 

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789  
Fax: 02 6773 3266
EMail: kgore4@xxxxxxxxxx

 




_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
 
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

 



_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/