Changes between Version 45 and Version 46 of Public/User_Guide/OmpSs-2


Ignore:
Timestamp:
Jun 14, 2019, 6:07:57 PM (5 years ago)
Author:
Pedro Martinez-Ferror
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Public/User_Guide/OmpSs-2

    v45 v46  
    148148}}}
    149149
    150 Additionally, you will need to change your running script in order to invoke the program through this trace.sh script. Although you can also edit your running script adding all the environment variables related with the instrumentation, it is preferable to use this extra script to easily change between instrumented and non-instrumented executions. When in need to instrument your execution, simply include trace.sh before the program invocation. Note that the **extrae.xml** file, which is used to configure the Extrae library to get a Paraver trace, is also needed.
     150Additionally, you will need to change your running script in order to invoke the program through this trace.sh script so that it looks like:
     151
     152`./trace.sh ./application`
     153
     154Although you can also edit your running script adding all the environment variables related with the instrumentation, it is preferable to use this extra script to easily change between instrumented and non-instrumented executions. When in need to instrument your execution, simply include trace.sh before the program invocation. Note that the **extrae.xml** file, which is used to configure the Extrae library to get a Paraver trace, is also needed.
    151155
    152156----
     
    378382}}}
    379383
    380 Additionally, you can get information related to hardware counters (PAPI). For this, first load the PAPI module:
     384Additionally, you can get information related to hardware counters via PAPI. For this, firstly load the PAPI module:
    381385
    382386`module load PAPI/5.6.0`
    383387
    384 and execute:
     388and then execute:
    385389
    386390`NANOS6=stats-papi taskset -c 12-23 ./03.multisaxpy_task 196608 8192 1`
     
    509513== Tracing with Extrae ==
    510514
    511 
     515To get traces of this benchmark using Extrae firstly load the corresponding module:
     516
     517`module load Extrae/3.6.1`
     518
     519and charge the Extrae environment in your active session:
     520
     521`source /usr/local/software/skylake/Stages/2018b/software/Extrae/3.6.1-ipsmpi-2018b-mt/etc/extrae.sh`
     522
     523Then copy a preconfigured ''extrae.xml'' file to instrument !OmpSs-2 to your current working directory ''multisaxpy/'':
     524
     525`cp /usr/local/software/skylake/Stages/2018b/software/Extrae/3.6.1-ipsmpi-2018b-mt/share/example/OMPSS/extrae.xml .`
     526
     527The next step is to create a new file ''trace.sh'':
     528
     529`touch trace.sh`
     530
     531with the necessary permission to be executed:
     532
     533`chmod +x trace.sh`
     534
     535and fill it with the following text:
     536
     537{{{#!bash
     538#!/bin/bash
     539export EXTRAE_CONFIG_FILE=extrae.xml
     540export NANOS6="extrae"
     541$*
     542}}}
     543
     544Now execute the benchmark keeping its original size but only 20 iterations with the following command:
     545
     546`taskset -c 12-23 ./trace.sh ./03.multisaxpy_task 16777216 8192 20`
    512547
    513548