Can you perhaps isolate/bind the job via MPI? i.e., submit HTCondor job as an mpirun --npernode 1 --bind-to core job.exe ...? I don't know though how/if HTCondor will respect binding and keep other tasks away. I assume it will/should.
From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Michael Pelletier [Michael.V.Pelletier@xxxxxxxxxxxx]
Sent: Thursday, December 15, 2016 2:14 PM
To: HTCondor-Users Mail List (htcondor-users@xxxxxxxxxxx)
Subject: [HTCondor-users] ASSIGN_CPU_AFFINITY - does it fence off a CPU? If not, is there a way to do so?
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!