hkaiser 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/ | GSoC2018: https://wp.me/p4pxJf-k1
<ste||ar-github>
hpx/thread_local_allocator 579a4aa Hartmut Kaiser: Adding thread local allocator and use it for future shared states
ste||ar-github has left #ste||ar [#ste||ar]
ste||ar-github has joined #ste||ar
ste||ar-github has left #ste||ar [#ste||ar]
<ste||ar-github>
[hpx] hkaiser opened pull request #3406: Adding thread local allocator and use it for future shared states (master...thread_local_allocator) https://github.com/STEllAR-GROUP/hpx/pull/3406
<ste||ar-github>
hpx/gcc8_warnings 732d999 John Biddiscombe: Fix unused param and extra ; warnings emitted by gcc 8.x
ste||ar-github has left #ste||ar [#ste||ar]
ste||ar-github has joined #ste||ar
<ste||ar-github>
[hpx] biddisco opened pull request #3407: Fix unused param and extra ; warnings emitted by gcc 8.x (master...gcc8_warnings) https://github.com/STEllAR-GROUP/hpx/pull/3407
ste||ar-github has left #ste||ar [#ste||ar]
_bibek_ has joined #ste||ar
bibek has quit [Ping timeout: 256 seconds]
nikunj97 has joined #ste||ar
<heller>
8192 node job submitted
<heller>
yay
david_pfander has joined #ste||ar
<zao>
heller: Why do I want to get a small manycore ARM board to do indeterminate things with? :)
<heller>
zao: burning money and energy?
<zao>
We did consider grabbing a pile of pi:s for our cloud, but more proper boards might be more appropraite.
<heller>
right
* zao
heads out into the maybe-rain
<heller>
I think the best reason to grab those arm boards is for the looks
<heller>
zao: you got rain? I am still waiting on it :/
daissgr has joined #ste||ar
<zao>
Possibly up to 15-20mm.
<heller>
all cloudy and windy, but no water from the heavens
<heller>
ha, at least something ;)
<heller>
zao: as for the cloud: why not go with one single potent X86 or power server?
<heller>
way more efficient, no?
<zao>
Yeah, more a bit of hybrid work with “emerging tech” project
<zao>
We run the cloud on old decommissioned cluster nodes and new Dell 1u machines, currently.
<zao>
Not sure what arch people need for their silly cloud software.
<zao>
I try my best to avoid it :)
jgolinowski has joined #ste||ar
<ms[m]1>
jgolinowski: here now
<ms[m]1>
Just the summary missing now?
<jgolinowski>
ms[m]1, well I am thinking of including some screenshot of the MartyCam app
<jgolinowski>
but yes, the summary is missing as well
<ms[m]1>
Ok
<ms[m]1>
Should I wait a bit still before reading it thoroughly?
<ms[m]1>
Do you think you'll have it more or less finished today?
<jgolinowski>
ms[m]1, so I think that what is there I want to be there
<jgolinowski>
and more details about the app are somewhat orthogonal to what is there currently so I think you can read it as it is
<ms[m]1>
OK, will do
<jgolinowski>
so maybe give me 10 minutes for the summary
<jgolinowski>
ms[m]1, also I wanted to somehow host the .html with the results of the DNN performance tests
<ms[m]1>
Yeah, I'll read it lateat in a couple of hours
<ms[m]1>
Could be nice
<jgolinowski>
but the blogger seems not to be the best for that because it tries to embed the html as the blog post and it looks very ugly
<jgolinowski>
So I thought maybe to put it under the stellar domain or sth like this?
<ms[m]1>
It's not possible to somehow have a custom page or files uploaded to blogger?
<jgolinowski>
I recently updated the readme so the build instructions should be up to date
<jgolinowski>
jbjnr, ^
<jbjnr>
nikunj97 has added support for runnint tests without using hpx::init and I'm using it on my dca project. It's nice. I have modified some headers to pull in the hpx_main when needed and apart fro theat tests that used to use std thread, now passs with hpx threads
<jbjnr>
jgolinowski: thanks
<jbjnr>
aha you did not clone martycam - is martycam just an example in there now?
<jbjnr>
I had a lot of animal noise ooutside the h0ouse last night and want to get martycam running again to find out what it was/is next time
<jgolinowski>
jbjnr, I cloned it initially but I needed an even smaller example at the beginning where I could copy the MartyCam piece by piece
<jgolinowski>
since it is more or less done now
<jgolinowski>
I can just paste the current version to my fork and update the PR
<jbjnr>
heller: unless you want to spend x months fixing it and rewriting it, then just state it as another use case that is being developed for heterogeneous computing ...
<jbjnr>
(with an outline of it's features/functionality)
<heller>
yeah ... let's keep it that way
<heller>
in that case: all measurements done
<heller>
check
<heller>
next: write the analysis of the results ;)
<heller>
one more try though...
<heller>
do we want to get HPX on compiler explorer?
<ms[m]1>
heller: why not? ? how much work does it require though
<ms[m]1>
jgolinowski_: just sent you an email with some small fixes
<heller>
ms[m]1: I guess someone needs to write the PR
<diehlpk_work>
The HPC dev room there is interesting
aserio has quit [Ping timeout: 255 seconds]
<zao>
diehlpk_work: I’d love to go to the easybuild meetup which is adjacent to fosdem, but I’m obligated to go to Norway to ski with NeIC that time of year :D