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

Re: [HTCondor-users] ASSIGN_CPU_AFFINITY - does it fence off a CPU? If not, is there a way to do so?

The way that I'd approach the problem would be to use cgroups to assign non-Conodr processes to a subset of your cpus and then assign the htcondor cgroup the remaining processor(s).


This shouldn't be reliant on systemd, but it's probably easier under systemd. For example, you might figure out how to set system.slice to everything but your favorite cores...

Tom Downes
Senior Scientist and Data CenterÂManager
Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin-Milwaukee

On Thu, Dec 15, 2016 at 4:14 PM, Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote:

Hi folks,


Iâm interested in insuring that an HTCondor job running on Linux can be assigned to a specific CPU in such a way that it gets it all to itself, and no other processes are allowed to run on that CPU even if the job isnât making use of the processor at that moment.


Iâm aware of ASSIGN_CPU_AFFINITY but from the documentation it appears that it works the other way around, such that the job can only use that CPU but other jobs might still be assigned to it.


Any suggestions? The idea is to protect the HTCondor tasks from other users of the system who havenât yet been migrated to submit their work via HTCondor, that being a work in progress. Thanks!


ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ -Michael Pelletier.

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

The archives can be found at: