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.
Â
Â
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) +49 511 762-17097
Callinstrasse 38
D-30167 Hannover,ÂÂGermany
Tel:Â
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@cs.wisc.edu 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/