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
Yorlik__ has joined #ste||ar
Yorlik_ has quit [Ping timeout: 246 seconds]
hkaiser has quit [Quit: Bye!]
HHN93 has joined #ste||ar
HHN93 has quit [Quit: Client closed]
sivoais has quit [Ping timeout: 240 seconds]
sivoais has joined #ste||ar
sivoais has quit [Ping timeout: 240 seconds]
sivoais has joined #ste||ar
sivoais has quit [Ping timeout: 264 seconds]
sivoais has joined #ste||ar
hkaiser has joined #ste||ar
<Aarya[m]> hkaiser: Can you point to the API that tells how many hpx threads are still running?
<hkaiser> Aarya[m]: ahh yes, one sec
<hkaiser> Aarya[m]: hpx::threads::get_thread_manager().get_thread_count();
<Aarya[m]> Thanks
<hkaiser> Aarya[m]: get_thread_count takes an optional argument (an enum type) that allows you to specify the type of threads to count (active, pending, terminated, etc.
<hkaiser> by default you get all of them
<Aarya[m]> Got it
<Aarya[m]> It says 2 threads are running after finalize
<hkaiser> Aarya[m]: one is the main thread, which is ok, but one is left that prevents HPX from exiting
<Aarya[m]> I'm not sure about that, i ran the hpxc example (simple thread create and then jpin) and they finishi fine and they also show 2 threads pending after finalize
<Aarya[m]> Also the number of threads (pending, terminated, active) is not consistent across different runs
<hkaiser> Aarya[m]: yah
<hkaiser> you should look at the thread count after your destructor has run