hkaiser changed the topic of #ste||ar to: The topic is '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/
weilewei has quit [Ping timeout: 260 seconds]
<hkaiser>
jaafar: pls feel free to merge wave to master or let me know if you want me to do it
<Yorlik>
At least the result is no longer horrible, if I didn't mess up the measuring. :)
K-ballo has quit [Quit: K-ballo]
K-ballo has joined #ste||ar
nikunj has joined #ste||ar
<nikunj>
simbergm, yt?
nikunj has quit [Ping timeout: 260 seconds]
nikunj has joined #ste||ar
<heller1>
Yorlik: the how long is the duration of your test?
<Yorlik>
Not very long - I'm eyeballing it, letting it run for a couple of mionutes. It's not like a fully scientific analysis
<Yorlik>
Also I still have a bug in my variance. I need to go ver it and make it correct, but the mean is precise - never had any issues with it. e.g. when I was padding a frame the times were exactly as expected.
<Yorlik>
When I made tests with the heap there were no signs of any leaks or something at least.
<Yorlik>
What still makes me wonder is, why the counters show so much idle time. Something is still strange.,
<Yorlik>
heller1 ^^
<heller1>
Yorlik: yeah ... they probably also include startup and shutdown, which adds some significant idle time
<Yorlik>
And the updater doesn't do much
<Yorlik>
How could I increase the number of loops in a parloop task?
<Yorlik>
Or tweak the task time
<Yorlik>
?
<heller1>
increase the number of loops?
<heller1>
just increase the iteration space?
<heller1>
I think your test looks good so far
<Yorlik>
Yes - I'd like to make the chinks of work larger
<Yorlik>
chunks
<Yorlik>
And : Can I add the performance counters to the ini? I hate doing it in the command line all the time
<Yorlik>
I failed trying to figure that out
<simbergm>
Yorlik: not sure about the ini file but you can pass command line parameters in the config vector to `hpx::init/start`
<simbergm>
looking for an example...
<simbergm>
that would be hardcoded in the application of course but at least saves you adding it manually all the time for testing purposes
<Yorlik>
I could make it a custom ini setting in my own ini then.,
<Yorlik>
I am thinking about writing an internal monito later which pulls the counters and tweaks the loop while the system is running.
<simbergm>
Yorlik: your tasks are about 150-200 us long which is very much on the short side for our schedulers (depends on the number of worker threads though)
<Yorlik>
The point is, I always have enough work.
<simbergm>
we usually recommend at least a ms as a conservative number since that usually gives you almost perfect efficiency with our schedulers
<Yorlik>
Because once a frame is done, the next immediately starts
<simbergm>
par(task).with(static_chunk_size(N)) to set the chunk size
<simbergm>
modulo namespaces
<Yorlik>
I don't understand how the loops can starve at all.
<simbergm>
task overheads
<Yorlik>
Just append to this: hpx::parallel::for_loop( hpx::parallel::execution::par( hpx::parallel::execution::task ), 0, m_e_type::maxindex, &update_entity<I> )
<simbergm>
most likely
<Yorlik>
I'll give it a shot
<hkaiser>
Yorlik: why par(task) btw - you're waiting for it to finish anyways
<simbergm>
yep, exactly
<Yorlik>
Could I give it a target task length instead of a static chunk size?
<Yorlik>
Like 500us or 1ms
<hkaiser>
Yorlik: you can if you use .with(auto_chunk_size(chrono::milliseconds(1))) or similar
<hkaiser>
but this will spend 1% of the iterations to measure how long it takes
<Yorlik>
I'll check both out
<Yorlik>
where do I append the "with"? after the policy?
<hkaiser>
par.with()
<hkaiser>
or par(task).with()
K-ballo has quit [Quit: K-ballo]
mdiers_ has joined #ste||ar
K-ballo has joined #ste||ar
<Yorlik>
Like this?
<Yorlik>
futures.push_back( // Collect futures from
<Yorlik>
I didn't find any info how to read the counter outputs
<hkaiser>
the docs say: "These lines have 6 fields, the counter name, the sequence number of the counter invocation, the time stamp at which this information has been sampled, the unit of measure for the time stamp, the actual counter value, and an optional unit of measure for the counter value."
<Yorlik>
Woops?
<Yorlik>
FFSRTFM
<Yorlik>
IC
<Yorlik>
So its sequence 9, at 80.. seconds, and the value is 2470*0.01 = 24.70 %
<hkaiser>
yes
<Yorlik>
OK - overlooked it in the Docs ... thanks for helping out - I need food now
<hkaiser>
any time
<Yorlik>
BBL :D
hkaiser has quit [Quit: bye]
mdiers_ has quit [Quit: mdiers_]
mdiers_ has joined #ste||ar
<Yorlik>
So - it's not much difference with 2,3 or 4 OS Threads, more gets inefficient and less also - in between only the idle rate changes, so I think I'm prtobably memory bound now, or is that a wrong conclusion?
<Yorlik>
However - I'll read up after meal ... BBL
nikunj97 has quit [Ping timeout: 268 seconds]
nikunj97 has joined #ste||ar
mdiers_ has quit [Remote host closed the connection]
mdiers_ has joined #ste||ar
<diehlpk_work>
simbergm, Will there be another hpx 1.4.1 rc?
<diehlpk_work>
Or when do we anticipate the final release?
hkaiser has joined #ste||ar
nikunj97 has quit [Ping timeout: 272 seconds]
nikunj97 has joined #ste||ar
<hkaiser>
simbergm: : #4380 should be fine now
<simbergm>
hkaiser: excellent, thanks! I'll give it a try
<simbergm>
diehlpk_work: assuming I don't screw anything up again there won't be another rc and I'll do the release on wednesday
<hkaiser>
simbergm: parsa repported that installing HPX doesn't work in Release if a PREFIX_PATH was specified
<hkaiser>
works fine in Debug
<simbergm>
mmh, `CMAKE_PREFIX_PATH`?
<hkaiser>
yes, that's what I meant
<simbergm>
or `CMAKE_INSTALL_PREFIX`?
<hkaiser>
sec
<simbergm>
can you ask him to open an issue?
<hkaiser>
parsa?
<simbergm>
hkaiser: ^
<hkaiser>
I asked him already, he will do that shortly, I hope
<simbergm>
hkaiser: thanks
RostamLog has joined #ste||ar
<hkaiser>
simbergm: #4392
<Yorlik>
When launching an action with parameters on a local id_type - does HPX automagically skip the serialization of the parameters?
rori has quit [Ping timeout: 246 seconds]
kordejong has quit [Ping timeout: 240 seconds]
simbergm has quit [Ping timeout: 240 seconds]
heller1 has quit [Ping timeout: 256 seconds]
<hkaiser>
Yorlik: yes
kordejong has joined #ste||ar
heller1 has joined #ste||ar
<hkaiser>
Yorlik: I modified auto_chunk_size to allow for specifying the number of iterations to use for measurement, see #4395