Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
doku:forge [2020/09/24 12:29] shdoku:forge [2022/11/04 10:14] – [Usage of map:] goldenberg
Line 1: Line 1:
-===== forge = map + ddt (VSC-3) =====+===== forge = map + ddt =====
 ==== Synopsis: ====  ==== Synopsis: ==== 
 <html> <font color=#cc3300><b>map</b></font> </html> and <html> <font color=#cc3300><b>ddt</b></font> </html> are ARM's (formerly Allinea's)  advanced tools for performance analysis, see [[https://developer.arm.com/tools-and-software/server-and-hpc/debug-and-profile/arm-forge]]. <html> <font color=#cc3300><b>map</b></font> </html> and <html> <font color=#cc3300><b>ddt</b></font> </html> are ARM's (formerly Allinea's)  advanced tools for performance analysis, see [[https://developer.arm.com/tools-and-software/server-and-hpc/debug-and-profile/arm-forge]].
-Licenses for up to 512 parallel tasks are available. Of additional note, <html> <font color=#cc3300><b>perf-report</b></font> </html> --- a related lightweight profiling tool --- has now been integrated into forge in more recent releases.+Licenses for up to 512 parallel tasks are available. Of additional note, [[doku:perf-report|perf-report]] --- a related lightweight profiling tool --- has now been integrated into forge in more recent releases.
  
  
Line 13: Line 13:
    #SBATCH -J map           #SBATCH -J map       
    #SBATCH -N 4    #SBATCH -N 4
-   #SBATCH -L allinea@vsc 
    #SBATCH --ntasks-per-node 16    #SBATCH --ntasks-per-node 16
    #SBATCH --ntasks-per-core  1    #SBATCH --ntasks-per-core  1
        
    module purge    module purge
-   module load  intel/18  intel-mpi/2018 allinea/20.1_FORGE+   module load  intel/18  intel-mpi/2018 arm/20.1_FORGE
        
    map --profile srun --jobid $SLURM_JOB_ID --mpi=pmi2 -n 64 ./a.out    map --profile srun --jobid $SLURM_JOB_ID --mpi=pmi2 -n 64 ./a.out
Line 24: Line 23:
 which generates a *.map file (note the mention of #tasks and #nodes together with the date/time stamp in the filename) that may then be analyzed via the gui, ie which generates a *.map file (note the mention of #tasks and #nodes together with the date/time stamp in the filename) that may then be analyzed via the gui, ie
  
-   ssh vsc3.vsc.ac.at -l my_uid -X+   ssh vsc4.vsc.ac.at -l my_uid -X
    cd wherever/the/map/file/may/be    cd wherever/the/map/file/may/be
        
Line 93: Line 92:
    my_uid@n305-044$  module load  intel/18  intel-mpi/2018  allinea/20.1_FORGE    my_uid@n305-044$  module load  intel/18  intel-mpi/2018  allinea/20.1_FORGE
    my_uid@n305-044$  cd wherever/my/app/may/be    my_uid@n305-044$  cd wherever/my/app/may/be
-   my_uid@n305-044$  srun --jobid 8909346 -n 16 hostname    ( just a dummy check to see whether all is set up correctly )+   my_uid@n305-044$  srun --jobid 8909346 -n 16 hostname    ( just a dummy check to see whether all is set up and working correctly )
    my_uid@n305-044$  ddt --connect srun --jobid 8909346 --mpi=pmi2 -n 64 ./a.out -arg1 -arg2   ( in the initial ddt-window a dialogue will pop up prompting for a Reverse Connection request; accept it and click Run and the usual debug session will start )    my_uid@n305-044$  ddt --connect srun --jobid 8909346 --mpi=pmi2 -n 64 ./a.out -arg1 -arg2   ( in the initial ddt-window a dialogue will pop up prompting for a Reverse Connection request; accept it and click Run and the usual debug session will start )
  
  • doku/forge.txt
  • Last modified: 2024/07/05 07:51
  • by grokyta