Changes between Version 35 and Version 36 of Public/User_Guide/OmpSs-2

Timestamp:

Jun 14, 2019, 3:39:05 PM (5 years ago)

Author:

Pedro Martinez-Ferror

Comment:

—

Public/User_Guide/OmpSs-2

@@ -5 +5 @@
 Table of contents:
 * [#QuickOverview Quick Overview] 
-* [#QuickSetuponDEEPSystem Quick Setup on DEEP System]
-* [#RepositorywithExamples Repository with Examples]
+* [#QuickSetuponDEEPSystemforaPureOmpSs-2Application Quick Setup on DEEP System for a Pure OmpSs-2 Application]
+* [#UsingtheRepositories Using the Repositories]
 * [#multisaxpybenchmarkOmpSs-2 multisaxpy benchmark (OmpSs-2)]
 * [#dot-productbenchmarkOmpSs-2 dot-product benchmark (OmpSs-2)]
@@ -49 +49 @@
 ----
 
-= Quick Setup on DEEP System =
-
-We highly recommend to log in a **cluster module (CM) node** to begin using !OmpSs-2.  To request an entire CM node for an interactive session, please execute the following command:
- `srun --partition=dp-cn --nodes=1 --ntasks=48 --ntasks-per-socket=24  --ntasks-per-node=48 --pty /bin/bash -i`   
+= Quick Setup on DEEP System for a Pure !OmpSs-2 Application =
+
+We highly recommend to interactively log in a **cluster module (CM) node** to begin using !OmpSs-2.  To request an entire CM node for an interactive session, please execute the following command to use all the 48 available threads:
+
+`srun -p dp-cn -N 1 -n 1 -c 48 --pty /bin/bash -i`
 
 Note that the command above is consistent with the actual hardware configuration of the cluster module with **hyper-threading enabled**.
 
 !OmpSs-2 has already been installed on DEEP and can be used by simply executing the following commands:
-* `modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/Core:$modulepath"`
-* `modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/Compiler/mpi/intel/2019.0.117-GCC-7.3.0:$modulepath"`
-* `modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/MPI/intel/2019.0.117-GCC-7.3.0/psmpi/5.2.1-1-mt:$modulepath"`
-* `export MODULEPATH="$modulepath:$MODULEPATH"`
-* `module load OmpSs-2` 
-
-Remember that !OmpSs-2 uses a **thread-pool** execution model which means that it **permanently uses all the threads** present on the system. Users are strongly encouraged to always check the **system affinity** by running the **NUMA command** `numactl --show`:
 {{{
-$ numactl --show
-policy: bind
-preferred node: 0
-physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 24 25 26 27 28 29 30 31 32 33 34 35 
-cpubind: 0 
-nodebind: 0 
-membind: 0 
+modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/Core:$modulepath"
+modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/Compiler/mpi/intel/2019.0.117-GCC-7.3.0:$modulepath"
+modulepath="/usr/local/software/skylake/Stages/2018b/modules/all/MPI/intel/2019.0.117-GCC-7.3.0/psmpi/5.2.1-1-mt:$modulepath"
+export MODULEPATH="$modulepath:$MODULEPATH"
+module load OmpSs-2
 }}}
-as well as the **Nanos6 command** `nanos6-info --runtime-details | grep List`:
+
+Remember that !OmpSs-2 uses a **thread-pool** execution model which means that it **permanently uses all the threads** present on the system. Users are strongly encouraged to always check the **system affinity** by running the **NUMA command** `srun numactl --show`:
 {{{
-$ nanos6-info --runtime-details | grep List
-Initial CPU List 0-11,24-35
+$ srun numactl --show
+policy: default
+preferred node: current
+physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 
+cpubind: 0 1 
+nodebind: 0 1 
+membind: 0 1 
+}}}
+as well as the **Nanos6 command** `srun nanos6-info --runtime-details | grep List`:
+{{{
+$ srun nanos6-info --runtime-details | grep List
+Initial CPU List 0-47
 NUMA Node 0 CPU List 0-35
-NUMA Node 1 CPU List 
+NUMA Node 1 CPU List 12-47
 }}}
 
-Notice that both commands return consistent outputs and, even though an entire node with two sockets has been requested, only the first NUMA node (i.e. socket) has been correctly bind.  As a result, only 48 threads of the first socket (0-11, 24-35), from which 24 are physical and 24 logical (hyper-threading enabled), are going to be utilised whilst the other 48 threads available in the second socket will remain idle. Therefore, **the system affinity showed above is not valid since it does not represent the resources requested via SLURM.**
-
 System affinity can be used to specify, for example, the ratio of MPI and !OmpSs-2 processes for a hybrid application and can be modified by user request in different ways:
-* Via SLURM. However, if the affinity does not correspond to the resources requested like in the previous example, it should be reported to the system administrators.
+* Via the command `srun` or `salloc`. However, if the affinity given by SLURM does not correspond to the resources requested, it should be reported to the system administrators.
 * Via the command `numactl`.
 * Via the command `taskset`.
@@ -92 +93 @@
 
 
-= Repository with Examples =
+= Using the Repositories =
 
 All the examples shown here are publicly available at [https://pm.bsc.es/gitlab/ompss-2/examples].  Users must clone/download each example's repository and then transfer it to a DEEP working directory.
@@ -98 +99 @@
 == System configuration ==
 
-Please refer to section [#QuickSetuponDEEPSystem Quick Setup on DEEP System] to get a functional version of !OmpSs-2 on DEEP. It is also recommended to run !OmpSs-2 on a cluster module (CM) node.
+Please refer to section [#QuickSetuponDEEPSystem Quick Setup on DEEP System] to get a functional version of !OmpSs-2 on DEEP. It is also recommended to run !OmpSs-2 via an interactive session on a cluster module (CM) node.
 
 == Building and running the examples ==