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
Yorlik_ has joined #ste||ar
Yorlik__ has quit [Ping timeout: 256 seconds]
hkaiser has quit [Quit: Bye!]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 265 seconds]
K-ballo1 is now known as K-ballo
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo1 is now known as K-ballo
hkaiser has joined #ste||ar
HHN93 has joined #ste||ar
<HHN93>
How do we find the number of cores to ideally launch the par algorithm?
<HHN93>
is their any API the OS provides for it?
<hkaiser>
HHN93: you can control the number of cores, but there is no perfect mechanism to automatically select it
<HHN93>
by default HPX chooses the number of physical cores, right?
<HHN93>
how does it find out the number of physical cores?
<hkaiser>
a) it looks at the hardware topology, and b) there is the --hpx:threads=N command line option that limits the number of cores used
<HHN93>
`a) it looks at the hardware topology`
<HHN93>
can you please briefly explain how this is done? or point me to the code which does it?