| 1 |
Process affinity in ARMCI comes into play for finding the optimal way to |
| 2 |
assign the data server thread that is used on many platforms to different |
| 3 |
physical processors on the node. This is only functional for the LINUX and |
| 4 |
LINUX64 platforms. |
| 5 |
|
| 6 |
Normally, ARMCI will run only 1 data server thread per node. It can be |
| 7 |
alternatively configured to run as many data servers as compute processes on a |
| 8 |
node. The way to enable one data server per compute process is by setting the |
| 9 |
environment variable ARMCI_NSERV_EQ_NPROC. |
| 10 |
|
| 11 |
These are two environment variables to control process affinity |
| 12 |
|
| 13 |
1. ARMCI_CHANGE_SERVER_AFFINITY |
| 14 |
|
| 15 |
if this is enabled in armci/src/GNUmakefile, data servers affinity is |
| 16 |
changed between different CPU's depending on the work load. Note that this |
| 17 |
is only applicable for the case where ARMCI_NSERV_EQ_NPROC is not defined. |
| 18 |
If both are defined, results may be undesirable. |
| 19 |
|
| 20 |
2. ARMCI_CHANGE_AFFINITY_GRANULARITY |
| 21 |
|
| 22 |
Data server changes its affinity based on its work load. The granularity |
| 23 |
at which to switch between CPU's can be changed with this evronment |
| 24 |
variable. The three values of this variable are SMALL, MEDIUM and LARGE. |
| 25 |
SMALL changes affinity in the order of milli-seconds of work load, MEDIUM |
| 26 |
does it at a granularity of 1 second and LARGE changes in the order of |
| 27 |
10's of seconds. |
| 28 |
|
| 29 |
Example: Please look at performance graph: |
| 30 |
|
| 31 |
affinity_performance.png |
| 32 |
|
| 33 |
which shows a case where changing affinity helps. The corresponding test for |
| 34 |
this is simple/affinity_test.c. |