PAR Technologies V5 manual Processes maxprocs, CPUmap map

This only comes into play, if the user does not define a sorting strategy explicitely via PSI_NODES_SORT. Be aware of the fact that using a batch-system like PBS or LSF *will* set the strategy explicitely, namely to NONE.

overbook { true yes 1 false no 0 }

If the argument is one of yes, true or 1, all nodes may be overbooked by the user using the PSI_OVERBOOK environment variable.

If the argument is one of no, false or 0, ParaStation will deny overbooking of the nodes, even if PSI_OVERBOOK is set.

It might be useful to prohibit the start of processes on a frontend machine since usually this machine is reserved for interactive work done by the users. When the execution of processes is forbidden on a distinct node, parallel task might be started from this node anyhow.

The default is to allow all nodes to run processes of parallel tasks.

processes maxprocs

Define the maximum number of processes per node.

This parameter can be set during runtime via the set maxproc directive within the ParaStation administration and management tool psiadmin(1).

pinProcs { true yes 1 false no 0 }

Enables or disables process pinning for compute tasks. If enabled, tasks will be pinned down to particular CPU-slots. The mapping between those CPU-slots and physical CPUs and cores is made using a mapping list. See CPUmap below.

The pinProcs parameter can be set during runtime via the set pinprocs directive within the ParaStation administration and management tool psiadmin(1).

bindMem { true yes 1 false no 0 }

This parameter must be set to true if nodes providing non-Uniform memory access (NUMA) should use 'local' memory for the tasks.

This parameter can be set during runtime via the set bindmem directive within the ParaStation administration and management tool psiadmin(1).

CPUmap { map }

Set the map used to assign CPU-slots to physical cores to map. Map is a quoted string containing a space-separated permutation of the number 0 to Ncore-1. Here Ncore is the number of physical cores available on this node. The number of cores within a distinct node may be determined via list hw. The first number in map is the number of the physical core the first CPU-slot will be mapped to, and so on.

This parameter can be set during runtime via the set bindmem directive within the ParaStation administration and management tool psiadmin(1).

supplGrps { true yes 1 false no 0 }

This parameter must be set to true if processes spawned by ParaStation should belong to all groups defined for this user. Otherwise, they will only belong to the primary group.

This parameter can be set during runtime via the set supplementaryGroups directive within the ParaStation administration and management tool psiadmin(1).

ParaStation5 Administrator's Guide 43