[hpx-users] PAW-ATM : Parallel Applications Workshop, Alternatives To MPI

[Biddiscombe, John A.]

Dear List

Please be aware that the "Parallel Applications Workshop, Alternatives To MPI" 
is open for submissions. It is a workshop held in conjunction with SC19 in 
Denver Nov 2019
https://sourceryinstitute.github.io/PAW/

Yours

JB


--
Dr. John Biddiscombe,email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users

Re: [hpx-users] PAW-ATM : Parallel Applications Workshop, Alternatives To MPI

[Biddiscombe, John A.]

I forgot to include the main text of the call - just FYI



Call for Papers

 PAW-ATM 2019:

Parallel Applications Workshop,
Alternatives To MPI+X

   Held in conjunction with SC 19, Denver, CO

   


Summary

Supercomputers are becoming increasingly complex due to the prevalence
of hierarchy and heterogeneity in emerging node and system
architectures.  As a result of these trends, users of conventional
programming models for scalable high-performance applications
increasingly find themselves writing applications using a mix of
distinct programming models-such as Fortran90, C, C++, MPI, OpenMP,
and CUDA-which are also often becoming more complex and
detail-oriented themselves. These trends negatively impact the costs
of developing, porting, and maintaining HPC applications.

Meanwhile, new programming models and languages are being developed
that strive to improve upon the status quo. This is accomplished by
unifying the expression of parallelism and locality across the system,
raising the level of abstraction, making use of modern language design
features, and/or leveraging the respective strengths of programmers,
compilers, runtimes, and operating systems.  These alternatives may
take the form of parallel programming languages (e.g., Chapel, Fortran
2018, Julia, UPC), frameworks for large-scale data processing and
analytics (e.g., Spark, Tensorflow, Dask), or libraries and embedded
DSLs that extend existing languages (e.g., Legion, COMPSs, SHMEM, HPX,
Charm++, UPC++, Coarray C++, Global Arrays).

The PAW-ATM workshop is designed to explore the expression of
applications in scalable parallel programming models that serve as an
alternative to the status quo.  It is designed to bring together
applications experts and proponents of high-level programming models
to present concrete and practical examples of using such alternative
models and to illustrate the benefits of high-level approaches to
scalable programming.


Scope and Aims

The PAW-ATM workshop is designed as a forum for exhibiting studies of
parallel applications developed using high-level parallel programming
models serving as alternatives to MPI+X-based programming. We
encourage the submission of papers and talks that describe practical
distributed-memory applications written using alternatives to MPI+X,
and include characterizations of scalability and performance,
expressiveness and programmability, as well as any downsides or areas
for improvement in such models. Our hope is to create a forum in which
architects, language designers, and users can present, learn about,
and discuss the state of the art in alternative scalable programming
models while also wrestling with how to increase their effectiveness
and adoption.  Beyond well-established HPC scientific simulations, we
also encourage submissions exploring artificial intelligence, big data
analytics, machine learning, and other emerging application areas.



Topics include, but are not limited to:

* Novel application development using high-level parallel programming
  languages and frameworks.

* Examples that demonstrate performance, compiler optimization, error
  checking, and reduced software complexity.

* Applications from artificial intelligence, data analytics,
  bioinformatics, and other novel areas.

* Performance evaluation of applications developed using alternatives
  to MPI+X and comparisons to standard programming models.

* Novel algorithms enabled by high-level parallel abstractions.

* Experience with the use of new compiler and runtime environments.

* Libraries using or supporting alternatives to MPI+X.

* Benefits of hardware abstraction and data locality on algorithm
  implementation.


Submissions

Submissions are solicited in two categories:

1) Full-length papers presenting novel research results:

  * Full-length papers will be published in the workshop proceedings.
Submitted papers must describe original work that has not appeared
in, nor is under consideration for, another conference or
journal. Papers shall be eight (8) pages minimum and not exceed
ten (10) including text, appendices, and figures.  Appendix pages
related to the reproducibility initiative dependencies, namely the
Artifact Description (AD) and Artifact Evaluation (AE), are not
included in the page count.

2) Extended abstracts summarizing preliminary/published results:

  * Extended abstracts will be evaluated separately and will not be
included in the published proceedings; they are intended to
propose timely communications of novel work that will be formally
submitted elsewhere at a later stage, and/or of already published
work that would be of interest to the PAW-ATM audience in terms of
topic and timeliness.  Extended abstracts shall not exceed four
(4) 

Re: [hpx-users] Benchmarks

[Adrian Serio]

Forwarding your question to the list.

On 4/29/2019 9:36 AM, kniedzie wrote:
>
> Adrian,
>
> thank you for you help. This information was helpful.
>
> Now I have problem building hpx with mpi. I receive this output:
>
> [ 54%] Linking CXX executable ../../../bin/test_client_1950
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in
> function `hpx::naming::gid_type::~gid_type()':
> /home/kn405499/tmp/hpx/hpx/runtime/actions/basic_action.hpp:171:
> multiple definition of `hpx_exported_plugins_list_hpx_factory';
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:13:
> first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in
> function `hpx_exported_plugins_list_hpx_registry':
> /opt/gcc/7.3.0/snos/include/g++/bits/basic_ios.h:462: multiple
> definition of `hpx_exported_plugins_list_hpx_registry';
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:14:
> first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in
> function `hpx_exported_plugins_force_load_hpx_factory':
> /opt/gcc/7.3.0/snos/include/g++/istream:607: multiple definition of
> `hpx_exported_plugins_force_load_hpx_factory';
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:13:
> first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in
> function `hpx_exported_plugins_force_load_hpx_registry':
> /opt/gcc/7.3.0/snos/include/g++/istream:608: multiple definition of
> `hpx_exported_plugins_force_load_hpx_registry';
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:14:
> first defined here
> /usr/bin/ld: ../../../lib/libhpx.a(runtime_support_server.cpp.o): in
> function `hpx::util::plugin::dll::LoadLibrary(hpx::error_code&, bool)':
> /home/kn405499/tmp/hpx/hpx/util/plugin/detail/dll_dlopen.hpp:297:
> warning: Using 'dlopen' in statically linked applications requires at
> runtime the shared libraries from the glibc version used for linking
> /usr/bin/ld: ../../../lib/libhpx.a(asio_util.cpp.o): in function
> `boost::asio::ip::basic_resolver::resolve(boost::asio::ip::basic_resolver_query
> const&)':
> /home/kn405499/libs/boost_1_69_0/include/boost/asio/detail/impl/socket_ops.ipp:3344:
> warning: Using 'getaddrinfo' in statically linked applications
> requires at runtime the shared libraries from the glibc version used
> for linking
> collect2: error: ld returned 1 exit status
> tests/regressions/build/CMakeFiles/test_client_1950.dir/build.make:111:
> recipe for target 'bin/test_client_1950' failed
> make[2]: *** [bin/test_client_1950] Error 1
> CMakeFiles/Makefile2:9348: recipe for target
> 'tests/regressions/build/CMakeFiles/test_client_1950.dir/all' failed
> make[1]: ***
> [tests/regressions/build/CMakeFiles/test_client_1950.dir/all] Error 2
> Makefile:138: recipe for target 'all' failed
> make: *** [all] Error 2
>
> My cmake configuration is:
>
> cmake -DBOOST_ROOT=/home/kn405499/libs/boost_1_69_0 \
>  -DHWLOC_ROOT=/home/kn405499/libs/hwloc-2.0.3/ \
>  -DCMAKE_INSTALL_PREFIX=/home/kn405499/libs/hpx_build_system_mpi \
>  -DCMAKE_BUILD_TYPE=RelWithDebInfo \
>  -DCMAKE_C_COMPILER=cc \
>  -DCMAKE_CXX_COMPILER=CC \
>  -DHPX_WITH_EXAMPLES=ON \
>  -DHPX_WITH_MALLOC=system \
>  -DHPX_WITH_STATIC_LINKING=OFF \
>  -DHPX_WITH_STATIC_EXE_LINKING=OFF \
>  -DHPX_WITH_PARCELPORT_MPI=ON \
>  -DMPI_C_COMPILER=cc \
>  -DMPI_CXX_COMPILER=CC \
>  -DHPX_WITH_TAU=OFF \
>  -DTAU_ROOT=/home/kn405499/libs/tau-2.25 \
>  -DTAU_ARCH=x86_64 \
>  -DTAU_OPTIONS=-mpi-pthread \
>  -DHPX_WITH_APEX=OFF \
>  -DAPEX_WITH_ACTIVEHARMONY=OFF \
>  -DAPEX_WITH_PAPI=OFF \
>  -DAPEX_WITH_MSR=OFF \
>  -DAPEX_WITH_OTF2=OFF \
>  -DACTIVEHARMONY_ROOT=/home/kn405499/libs/harmony-4.6.0/ \
>  /home/kn405499/tmp/hpx
>
> Do you now how to solve this issue?
>
> Best,
>
> Karol
>
> On 1/22/19 5:56 PM, Adrian Serio wrote:
>>
>> Karol,
>>
>> Our team did produce a paper on the inncabs benchmarks:
>>
>> http://stellar.cct.lsu.edu/pubs/hpcmaspa2016.pdf
>>
>> https://github.com/STEllAR-GROUP/inncabs
>>
>> Perhaps this is helpful to you?
>>
>> Adrian
>>
>> On 1/18/2019 11:08 AM, k.niedzielew...@icm.edu.pl wrote:
>>> Dear HPX team,
>>>
>>> I am currently writing my master thesis and I am planning to use HPX. I 
>>> already installed it on our system. Do you posses HPX benchmarking 
>>> software? Is it possible to acquire it from you? I need it for testing.
>>>
>>> Best regards
>>>
>>> Karol Niedzielewski
>>>
>>> ___
>>> hpx-users mailing list
>>> hpx-users@stellar.cct.lsu.edu
>>> https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
>> -- 
>> Adrian Serio
>> Scientific Program Coordinator
>> 2118 Digital Media Center
>> 225.578.8506

-- 
Adrian Serio
Scientific Program Coordinator
2118 Digital Media 

Re: [hpx-users] Benchmarks

[Thomas Heller]

Hi Karol,

The below looks like you are on a Cray machine, forcing static linking
to off (it is off by default anyway) and using the Cray compiler
wrapper, which adds some special static linking flags by default.
This is the reason for the error you are seeing. CMake thinks it needs
to link dynamically, setting its own set of flags, the cray compiler
tries to link statically.
For compilation with the Cray compiler wrappers, I recommend using our
toolchain files linked here:
https://stellar-group.github.io/hpx/docs/sphinx/latest/html/manual/building_hpx.html#cmake-toolchains-shipped-with-hpx

I hope this helps. Please purge your build directory before trying.

On Mon, Apr 29, 2019 at 4:56 PM Adrian Serio  wrote:
>
> Forwarding your question to the list.
>
> On 4/29/2019 9:36 AM, kniedzie wrote:
>
> Adrian,
>
> thank you for you help. This information was helpful.
>
> Now I have problem building hpx with mpi. I receive this output:
>
> [ 54%] Linking CXX executable ../../../bin/test_client_1950
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in 
> function `hpx::naming::gid_type::~gid_type()':
> /home/kn405499/tmp/hpx/hpx/runtime/actions/basic_action.hpp:171: multiple 
> definition of `hpx_exported_plugins_list_hpx_factory'; 
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:13:
>  first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in 
> function `hpx_exported_plugins_list_hpx_registry':
> /opt/gcc/7.3.0/snos/include/g++/bits/basic_ios.h:462: multiple definition of 
> `hpx_exported_plugins_list_hpx_registry'; 
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:14:
>  first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in 
> function `hpx_exported_plugins_force_load_hpx_factory':
> /opt/gcc/7.3.0/snos/include/g++/istream:607: multiple definition of 
> `hpx_exported_plugins_force_load_hpx_factory'; 
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:13:
>  first defined here
> /usr/bin/ld: ../../../lib/libtest_server_1950.a(server_1950.cpp.o): in 
> function `hpx_exported_plugins_force_load_hpx_registry':
> /opt/gcc/7.3.0/snos/include/g++/istream:608: multiple definition of 
> `hpx_exported_plugins_force_load_hpx_registry'; 
> ../../../lib/libhpx.a(runtime_support.cpp.o):/home/kn405499/tmp/hpx/src/runtime/components/runtime_support.cpp:14:
>  first defined here
> /usr/bin/ld: ../../../lib/libhpx.a(runtime_support_server.cpp.o): in function 
> `hpx::util::plugin::dll::LoadLibrary(hpx::error_code&, bool)':
> /home/kn405499/tmp/hpx/hpx/util/plugin/detail/dll_dlopen.hpp:297: warning: 
> Using 'dlopen' in statically linked applications requires at runtime the 
> shared libraries from the glibc version used for linking
> /usr/bin/ld: ../../../lib/libhpx.a(asio_util.cpp.o): in function 
> `boost::asio::ip::basic_resolver::resolve(boost::asio::ip::basic_resolver_query
>  const&)':
> /home/kn405499/libs/boost_1_69_0/include/boost/asio/detail/impl/socket_ops.ipp:3344:
>  warning: Using 'getaddrinfo' in statically linked applications requires at 
> runtime the shared libraries from the glibc version used for linking
> collect2: error: ld returned 1 exit status
> tests/regressions/build/CMakeFiles/test_client_1950.dir/build.make:111: 
> recipe for target 'bin/test_client_1950' failed
> make[2]: *** [bin/test_client_1950] Error 1
> CMakeFiles/Makefile2:9348: recipe for target 
> 'tests/regressions/build/CMakeFiles/test_client_1950.dir/all' failed
> make[1]: *** [tests/regressions/build/CMakeFiles/test_client_1950.dir/all] 
> Error 2
> Makefile:138: recipe for target 'all' failed
> make: *** [all] Error 2
>
> My cmake configuration is:
>
> cmake -DBOOST_ROOT=/home/kn405499/libs/boost_1_69_0 \
>  -DHWLOC_ROOT=/home/kn405499/libs/hwloc-2.0.3/ \
>  -DCMAKE_INSTALL_PREFIX=/home/kn405499/libs/hpx_build_system_mpi \
>  -DCMAKE_BUILD_TYPE=RelWithDebInfo \
>  -DCMAKE_C_COMPILER=cc \
>  -DCMAKE_CXX_COMPILER=CC \
>  -DHPX_WITH_EXAMPLES=ON \
>  -DHPX_WITH_MALLOC=system \
>  -DHPX_WITH_STATIC_LINKING=OFF \
>  -DHPX_WITH_STATIC_EXE_LINKING=OFF \
>  -DHPX_WITH_PARCELPORT_MPI=ON \
>  -DMPI_C_COMPILER=cc \
>  -DMPI_CXX_COMPILER=CC \
>  -DHPX_WITH_TAU=OFF \
>  -DTAU_ROOT=/home/kn405499/libs/tau-2.25 \
>  -DTAU_ARCH=x86_64 \
>  -DTAU_OPTIONS=-mpi-pthread \
>  -DHPX_WITH_APEX=OFF \
>  -DAPEX_WITH_ACTIVEHARMONY=OFF \
>  -DAPEX_WITH_PAPI=OFF \
>  -DAPEX_WITH_MSR=OFF \
>  -DAPEX_WITH_OTF2=OFF \
>  -DACTIVEHARMONY_ROOT=/home/kn405499/libs/harmony-4.6.0/ \
>  /home/kn405499/tmp/hpx
>
> Do you now how to solve this issue?
>
> Best,
>
> Karol
>
> On 1/22/19 5:56 PM, Adrian Serio wrote:
>
> Karol,
>
> Our team did produce a paper on the inncabs benchmarks:
>
> http://stellar.cct.lsu.edu/pubs/hpcmaspa2016.pdf
>
> https://github.com/STEllAR-GROUP/inncabs
>
> Perhaps this