Re: [HTCondor-users] OMP_NUM_THREADS forced to request_cpus value

[John M Knoeller <johnkn@xxxxxxxxxxx>]

Sorry, there is no way to disable or override this behavior. 

 

I think it would be reasonable to change HTCondor so that we will only set it if it was

not set by the job, or if set to a value larger than the CPUs value for the slot.

 

would that solve your problem?

 

-tj

 

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Alex Nitz
Sent: Wednesday, March 14, 2018 3:54 PM
To: htcondor-users@xxxxxxxxxxx
Subject: [HTCondor-users] OMP_NUM_THREADS forced to request_cpus value

 

Hi All,

 

We are trying to use condor with jobs that spawn processes through forking and which may use libraries which themselves link to openmp. It appears that condor is forcing the OMP_NUM_THREADS environment variable to equal the "request_cpu" value. Unfortunately, this causes our processes to *each* spawn that many threads and overload the machine. 

 

We've tried to set the OMP_NUM_THREADS variable and have this passed to our jobs, but it appears that the code introduced in the following ticket overrides anything we set.

 

https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4884

 

Is anyone aware of some way to disable this? It would be useful to have a way to disable this condor behavior by default.

 

-Alex

 

-- 

Dr. Alexander Nitz
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Callinstrasse 38
D-30167 Hannover,  Germany
Tel: +49 511 762-17097