Assembly: Microsoft.Hpc.Scheduler.Properties (in Microsoft.Hpc.Scheduler.Properties.dll)
|AllJobs||Directs the HPC Node Manager Service to set the processor affinity for any task to which an entire node is not allocated. This setting is the best choice for jobs such as parameter sweeps and Service-Oriented Architecture (SOA) jobs, for which multiple instances of the application can run per node and for which you want these instances to be isolated from each other. This setting corresponds to the affinity behavior in Windows HPC Server 2008.|
|NoJobs||Directs the HPC Node Manager Service never to set processor affinity on any task. This setting is excellent choice if you are running MPI tasks and want to be sure that you can use the –affinity option for the mpiexec command even when jobs share nodes. This setting is also useful for applications that set their own processor affinity. This setting corresponds to the affinity behavior in Windows Compute Cluster Server 2003.|
|NonExclusiveJobs||Directs the HPC Node Manager Service not to set affinity on jobs that are marked as exclusive. This setting is the ideal choice for jobs that contain only one task, because this setting enables that task to take advantage of all cores on the nodes to which the task is assigned. This setting provides new affinity-setting behavior for Windows HPC Server 2008 SP1 and is the default setting for Windows HPC Server 2008 SP1, Windows HPC Server 2008 SP2, and Windows HPC Server 2008 R2, because this setting provides the generally preferred behavior for MPI tasks, which are most likely to be sensitive to affinitization. When you use this setting, MPI tasks in exclusive jobs can take advantage of the –affinity option of the mpiexec command even if the task is not allocated an entire node.|
In Windows HPC Server 2008, processor affinity is set in the following ways:
Through the HPC Node Manager Service.
Through the mpiexec command, which provides an -affinity option to set processor affinity on all of the ranks within a Message Passing Interface (MPI) application.
Processor affinity cannot be set by both of the above methods simultaneously. To enable you to control how processor affinity is set, particularly for MPI tasks and exclusive tasks, Windows HPC 2008 SP1 provides an AffinityType cluster-wide parameter. The values of this enumeration correspond to the possible settings for that cluster-wide parameter.
Platform Note: This enumeration was introduced in Windows HPC Server 2008 SP1, and is not supported in previous versions. For Windows HPC Server 2008 R2, both the HPC Node Manager Service and mpiexec command can set affinity. But it is recommended that you continue to use the default affinity mode of NonExclusiveJobs so that the node manager does not limit the number of processors allocated to the task.
Development PlatformsWindows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
Target PlatformsWindows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, with HPC Pack Client Utilities