ity before other tasks with a higher priority, if
these higher priority tasks just was not scheduled for now
(think Priority-Queue functionality).
Is there a way to intervene with the hpx runtime on such a
low level?
Thanks in advance,
Kilian Werner
P.S.: The problem could also be sol
re.get()" from the loop and
instead using
"hpx::lcos::wait_all(containerImageFutures);" before
calling the loop the output is:
[15:58:55] Size: 2
[15:58:55] ForEach Loop verifies existence of 0 while
obvserving length 2
[15:58:55] ForEach Loop verifies existence of 1 w
Hello Steve and Hartmut,
following your discussion about remote dependencies
between futures has left me with two questions:
1.) If we pass a future as an argument to a remote
function call, is the actual call of the function delayed,
until the future becomes ready?
So does:
hpx::future arg
policies, executors, target
components etc.) but can I unpack a parameter through the
thread_data* ?
Thanks in Advance,
Kilian Werner
___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
jects) and it's not
really pretty either. I also suspect it's overhead to be
more severe than for a nicely integrated priority queue
backend, which is what I want to evaluate, actually.
If you have ideas for better solutions, I would be very
glad to try them.
Best regards,
Kilian Werner
___
dealt
with one after the other we went to performance counters
for more detailed profiling.
Thanks,
Kilian Werner
On Tue, 9 Jan 2018 08:47:12 -0600
"Hartmut Kaiser" <hartmut.kai...@gmail.com> wrote:
> Kilian,
>
> Was this slowdown happening always or did it just
>
to trace HPX in
a vampir trace / gantt-chart like fashion?
Best regards,
Kilian Werner
___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
.
>>
>> Regards Hartmut
>> ---
>> http://stellar.cct.lsu.edu
>> https://github.com/STEllAR-GROUP/hpx
>>
>>
>>> -Original Message-
>>> From: hpx-users-boun...@stellar.cct.lsu.edu >> boun...@stellar.cct.lsu.edu> On Beha
a few hundred bytes. We do not
supply a configuration or any command line parameters
beyond hpx:threads. The application is run on a single
node, without remote calls of any kind.
Thank you for your time.
Kilian Werner
___
hpx-users ma