The three strategies are: -1: Use =ASSIGN_CPU_AFFINITY= +1: Use ASSIGN_CPU_AFFINITY 2: Use cgroups 3: Use startd policy expressions to monitor cores used, and place jobs on hold that use more cores than were requested/allocated. @@ -34,7 +34,7 @@ This configuration works on any operating system (Linux, Windows, MacOS), does not require root/administrator access, and continues to work even if there is more than one startd running per machine (and thus is applicable in a glide-in scenario). Append the below into the condor_config file(s) on your execute machines to 1) advertise the number of CPU cores used by the job in the -slot ad as attribute CpusUsage, and to 2) place jobs on hold that use more cores than requested. +slot ad as attribute =CpusUsage=, and to 2) place jobs on hold that use more cores than requested. {code} #