Changes between Version 41 and Version 42 of Public/User_Guide/OmpSs-2


Ignore:
Timestamp:
Jun 14, 2019, 4:52:08 PM (5 years ago)
Author:
Pedro Martinez-Ferror
Comment:

Legend:

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

    v41 v42  
    185185`ssh -X USERNAME@deep.fz-juelich.de`
    186186
    187 and from there go to the ''multisaxpy'' folder
     187and from there open the ''multisaxpy''
    188188
    189189`cd /work/cdeep/USERNAME/multisaxpy`
     
    216216}}}
    217217
    218 Now you should be able to clean, build and execute this benchmark consisting of 7 implementations via the command `make`:
     218Now you should be able to clean, build and execute this benchmark via the command `make`:
    219219{{{
    220220$ make clean
     
    260260}}}
    261261
     262== Override the Number of Threads Used ==
     263
     264Let's have a closer look at the third implementation ''03.multisaxpy_task'' which took 0.648536 seconds to finish using 48 threads.
     265
     266A full CM node features 48 threads (0-47) divided in two sockets: 0-11,24-35 for the first socket and 12-23,36-47 for the second socket.  **Notice that they are indeed not consecutive! **
     267
     268We can change the threads used by !OmpSs-2 with the Linux command `taskset`.  For example, the command to run this binary with 24 threads interleaved between the two sockets would be:
     269
     270`taskset -c 0-23 ./03.multisaxpy_task 16777216 8192 100`
     271
     272Similarly, to run this benchmark using all the 24 threads of the second socket use the following command:
     273
     274`taskset -c 12-23,36-47 ./03.multisaxpy_task 16777216 8192 100`
     275
     276You can also try to run this example with only 12 threads of the first socket:
     277
     278`taskset -c 0-11 ./03.multisaxpy_task 16777216 8192 100`
     279
     280or 12 threads interleaved between the two sockets:
     281
     282`taskset -c 0-5,12-17 ./03.multisaxpy_task 16777216 8192 100`
     283
     284Changing the number of threads assigned to !OmpSs-2 affects the performance of the application:
     285{{{
     286$ ./03.multisaxpy_task 16777216 8192 100
     287size: 16777216, bs: 8192, iterations: 100, time: 0.653537, performance: 2.56714
     288$ taskset -c 0-23 ./03.multisaxpy_task 16777216 8192 100
     289size: 16777216, bs: 8192, iterations: 100, time: 0.686265, performance: 2.44471
     290$ taskset -c 12-23,36-47 ./03.multisaxpy_task 16777216 8192 100
     291size: 16777216, bs: 8192, iterations: 100, time: 0.650363, performance: 2.57967
     292$ taskset -c 0-11 ./03.multisaxpy_task 16777216 8192 100
     293size: 16777216, bs: 8192, iterations: 100, time: 0.55417, performance: 3.02745
     294$ taskset -c 0-5,12-17 ./03.multisaxpy_task 16777216 8192 100
     295size: 16777216, bs: 8192, iterations: 100, time: 0.705859, performance: 2.37685
     296}}}
     297
     298
     299
    262300== References ==
    263301