aserio changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
hkaiser has quit [Quit: bye]
diehlpk has joined #ste||ar
diehlpk has quit [Remote host closed the connection]
K-ballo has quit [Quit: K-ballo]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
eschnett has joined #ste||ar
vamatya_ has joined #ste||ar
vamatya_ has quit [Ping timeout: 240 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
bikineev has joined #ste||ar
bikineev has quit [Read error: Connection reset by peer]
bikineev has joined #ste||ar
bikineev has quit [Remote host closed the connection]
bikineev has joined #ste||ar
bikineev has quit [Read error: Connection reset by peer]
bikineev has joined #ste||ar
mcopik has joined #ste||ar
bikineev has quit [Remote host closed the connection]
Matombo has joined #ste||ar
david_pfander1 has joined #ste||ar
david_pfander has quit [Ping timeout: 276 seconds]
Matombo has quit [Remote host closed the connection]
Matombo has joined #ste||ar
bikineev has quit [Ping timeout: 255 seconds]
hkaiser has joined #ste||ar
bikineev has joined #ste||ar
<jbjnr>
hkaiser: question? The tcp threads you mentioned yesterday. Are they used just during startup to get all the nodes together into a group so we know how many localities are being used etc?
<hkaiser>
those threads are used to call into the socket layer of the os
<jbjnr>
ok, bu if I got rid of them, what would break
<hkaiser>
shrug
<hkaiser>
if you disable TCP alltogether they should not be needed, not sure even if they are created in that case to begin with
<jbjnr>
can you remember where they are created (which class administers them?)
<hkaiser>
io_service_pool
<hkaiser>
util::
<jbjnr>
hmm. I th0ought that was used by the timer and io threads
<hkaiser>
jbjnr: there is a config setting allowing to control the number of tcp threads created, easiest may be to set that to 0
<jbjnr>
ooh. great
<hkaiser>
same thing tcp uses it as well
<hkaiser>
hpx.threadpools.parcel_pool_size
<jbjnr>
if we disable networking, then does any synchronization take place between nodes on program start?
<github>
[hpx] AntonBikineev created nondefault_ctor_ser (+1 new commit): https://git.io/v76WU
<github>
hpx/nondefault_ctor_ser 1b6b227 AntonBikineev: Serializing collections with non-default constructible data
<github>
[hpx] AntonBikineev opened pull request #2805: Serializing collections with non-default constructible data (master...nondefault_ctor_ser) https://git.io/v76WI
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
david_pf_ has quit [Quit: david_pf_]
EverYoun_ has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
EverYoun_ has quit [Ping timeout: 276 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]