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
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
K-ballo has quit [Client Quit]
K-ballo has joined #ste||ar
Yorlik__ has joined #ste||ar
Yorlik_ has quit [Ping timeout: 260 seconds]
hkaiser has quit [Quit: Bye!]
<gonidelis[m]> K-ballo yt?
hkaiser has joined #ste||ar
<K-ballo> gonidelis[m]: now
hkaiser has quit [Quit: Bye!]
<gonidelis[m]> Do compiles require other threading systems to make execution::par actually run in parallel? https://godbolt.org/z/17evaPfsa
<gonidelis[m]> I know gcc say sth like "if you don't install tbb natively it might not parallize your code" or sth in those lines
<gonidelis[m]> says*
<gonidelis[m]> but i was wondering. can i use posix?
<gonidelis[m]> threads*
diehlpk has joined #ste||ar
diehlpk has quit [Quit: Leaving.]
diehlpk has joined #ste||ar
diehlpk has quit [Quit: Leaving.]
<K-ballo> a bounded thread pool with just one pool?
<K-ballo> *with just one thread
<gonidelis[m]> K-ballo: how do you know it's a bounded tp?
<gonidelis[m]> my question is coming from hpx i understand that our par algos run HPX core underneath
<gonidelis[m]> but when i use gcc or llvm and i just slap std::execution::par in there
<gonidelis[m]> what threading system is being used underneath?
<gonidelis[m]> and where do i find this info
<gonidelis[m]> K-ballo: like what's the difference with this one
hkaiser has joined #ste||ar
<pansysk75[m]> hkaiser: Any easy way to add a thread description with a thread spawned using hpx::async?
<pansysk75[m]> I'm trying to debug but it's somehow inheriting "hpx_main" as a description for most spawned threads
<pansysk75[m]> ok found it, hpx::annotated_function seems to do what i need
<hkaiser> pansysk75[m]: yes
<hkaiser> create this on the stack of the function you want to assign a name to: async([]() { scoped_annotation _("foobar); ...});
<pansysk75[m]> Thanks, I now remember also using those back when I was trying to use intel's vtune
<hkaiser> executors have something similar as well, for all threads they create
hkaiser has quit [Quit: Bye!]