This document will describe the work done under the PRACE-4IP extension. This task is dedicated to provide useful information on application *performance and energy usage* on next generation systems on the path towards exacsale. It will be caried out running the accelerated UEABS on PCP systems to obtain energy metrics on *OpenPower+GPU, Xeon Phi and FPGA*.
Organisation is publicly available to anyone interrested in the project and rely on the following tools:
* a slack channel for chat purpose: `PRACE PCP slack channel`_ , ask `Victor Cameo Ponz`_ for registration link.
* a mailing list: prace-4ip-wp7.extension@fz-juelich.de, subscribe here: `mailing list registration page`_.
* this documentation.
The following timeline will be followed to lead this task:
#. white paper indicating what applications will be run on which prototypes (meeting the PRACE milestone **MS33 due by August 2017/M4**)
#. grant access to machines (cut off September 2017 )
#. run codes (cut off October/November)
#. gather results and report *Applications Performance and Energy Usage* (this adresses the PRACE deliverable **D7.7 due by December 2017/M8**)
This document will describe the work done under the PRACE-4IP extension. This
task is dedicated to provide useful information on application *performance and
energy usage* on next generation systems on the path towards exacsale. It will
be caried out running the accelerated UEABS on PCP systems to obtain energy metrics
on *OpenPower+GPU, Xeon Phi and FPGA*.
PCP systems availables
----------------------
...
...
@@ -31,7 +24,7 @@ The table :ref:`table-pcp-systems` sums up systems and availability:
.. note:: More detailed information can be found for :ref:`e4_gpu`, :ref:`atos_knl` and :ref:`maxeler_fpga` systems. It includes, hardware description, registration procedures, and energy hardware and tool information.
.. note:: More detailed information can be found for :ref:`e4_gpu`, :ref:`atos_knl`
and :ref:`maxeler_fpga` systems. It includes, hardware description,
registration procedures, and energy hardware and tool information.
Code definition
---------------
Two sets of codes will be run. One will focus on giving metrics on multiple machines for UEABS codes while the other will focus on porting specific kernels to the KNL machine sampling energy impact on modification.
Two sets of codes will be run. One will focus on giving metrics on multiple machines
for UEABS codes while the other will focus on porting specific kernels to the KNL
machine sampling energy impact on various parameters.
UEABS
^^^^^
The table :ref:`table-code-definition` shows all codes available with UEABS (regular and accelerated). It states for each codes, tageted architechures and BCOs. Note that due to tight deadlines, efforts to port codes to new architechures will have to be minimal.
The table :ref:`table-code-definition` shows all codes available with UEABS
(regular and accelerated). It states for each codes, tageted architechures and BCOs.
Note that due to tight deadlines, efforts to port codes to new architechures will
