hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
hkaiser has joined #ste||ar
hkaiser has quit [Quit: Bye!]
Yorlik_ has joined #ste||ar
K-ballo has quit [Ping timeout: 240 seconds]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
Yorlik_ has quit [Read error: Connection reset by peer]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
<satacker[m]> \md
<hkaiser> satacker[m]: hey
<hkaiser> I think it is done now, will approve later today - just didn't have time to look into it more closely
<gonidelis[m]> hkaiser: any special flags needed for this to be able to run as a separate executable ? https://github.com/STEllAR-GROUP/hpx/blob/master/examples/quickstart/executor_with_thread_hooks.cpp
<gonidelis[m]> Also, pansysk75 wants to reproduce the diagram regarding the chunk/execution time from here
<gonidelis[m]> should we be using annotations and visualize it on our own, or should we go be to vtune by default?
<hkaiser> gonidelis[m]: anything goes
<gonidelis[m]> hkaiser: what about the flags?
<hkaiser> what flags?
<gonidelis[m]> what flags should be used for the hpx build
<hkaiser> depends on what you want
<gonidelis[m]> i only know HPX_WITH_ITTNOTIFY
<hkaiser> yah, that's needed for vtune integration
<gonidelis[m]> collect traces for vtune
<gonidelis[m]> just that
<hkaiser> there is HPX_WITH_ITTNOTIFY at compile time and --hpx:ini=hpx.use_itt_notify!=1 at runtime
<gonidelis[m]> great!
<gonidelis[m]> thanks!
hkaiser has quit [Quit: Bye!]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo