% docx2tex --- ``Garbage In, Garbage Out'' 
% 
% docx2tex is Open Source and 
% you can download it on GitHub: 
% https://github.com/transpect/docx2tex 
% 
\documentclass{scrbook} 
\usepackage{graphicx} 
\usepackage{hyperref} 
\usepackage{multirow} 
\usepackage{tabularx} 
\usepackage{color} 
\usepackage{amsmath} 
\usepackage{amssymb} 
\usepackage{amsfonts} 
\usepackage{amsxtra} 
\usepackage{wasysym} 
\usepackage{isomath} 
\usepackage{mathtools} 
\usepackage{txfonts} 
\usepackage{upgreek} 
\usepackage{enumerate} 
\usepackage{tensor} 
\usepackage{pifont} 
 
 
 
 
 
\usepackage[ngerman]{babel}
\definecolor{color-1}{rgb}{0.91,0.9,0.9}
\definecolor{color-2}{rgb}{1,1,1}
\definecolor{color-3}{rgb}{0.85,0.85,0.85}
\definecolor{color-4}{rgb}{1,0,0}
\begin{document}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image1.jpeg}

\textbf{E-Infrastructures}

\textbf{H2020-EINFRA-2014-2015}

\textbf{EINFRA-4-2014: Pan-European High Performance Computing}

\textbf{Infrastructure and Services}

\textbf{PRACE-4IP}

\textbf{PRACE Fourth Implementation Phase Project}\label{ref-0001}

\textbf{Grant Agreement Number: \label{ref-0002}EINFRA-653838}

\textbf{D7.5}\label{ref-0003}

\textbf{Application performance on accelerators}\label{ref-0004}

\textbf{\textit{Final }} \label{ref-0005}

Version: \label{ref-0006}1.0

Author(s): \label{ref-0007}Victor Cameo Ponz, CINES

Date: 24.03.2016

\textbf{Project and Deliverable Information Sheet\label{ref-0008}}

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.23\linewidth-2\tabcolsep}
p{\dimexpr 0.29\linewidth-2\tabcolsep}
p{\dimexpr 0.48\linewidth-2\tabcolsep}}
\multirow{7}{*}{\textbf{PRACE Project}}& \multicolumn{2}{l}{\textbf{Project Ref. №:} \textbf{{\hyperref[ref-0002]{EINFRA-653838}}}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Project Title:} \textbf{{\hyperref[ref-0001]{PRACE Fourth Implementation Phase Project}}}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Project Web Site:} \href{http://www.prace-project.eu}{http://www.prace-project.eu}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Deliverable ID:} {\textless} \textbf{{\hyperref[ref-0003]{D7.5}}}{\textgreater}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Deliverable Nature:} {\textless}DOC\_TYPE: Report / Other{\textgreater}} \\
\cline{2-2}\cline{3-3} & \multirow{1}{*}{\textbf{Dissemination Level:}\par PU}& \textbf{Contractual Date of Delivery:}\par $31 / 03 / 2017$ \\
\cline{3-3} & & \textbf{Actual Date of Delivery:}\par DD / Month / YYYY \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{EC Project Officer:} \textbf{Leonardo Flores A\~{n}over}} \\

\end{tabularx}

\end{table}

* - The dissemination level are indicated as follows: \textbf{PU} -- Public, \textbf{CO} -- Confidential, only for members of the consortium (including the Commission Services) \textbf{CL} -- Classified, as referred to in Commission Decision 2991/844/EC.

\textbf{Document Control Sheet\label{ref-0009}}

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.23\linewidth-2\tabcolsep}
p{\dimexpr 0.29\linewidth-2\tabcolsep}
p{\dimexpr 0.48\linewidth-2\tabcolsep}}
\multirow{5}{*}{\textbf{Document}}& \multicolumn{2}{l}{\textbf{Title:} \textbf{{\hyperref[ref-0004]{Application performance on accelerators}}}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{ID:} \textbf{{\hyperref[ref-0003]{D7.5}}} } \\
\cline{2-2}\cline{3-3} & \textbf{Version:} {\textless}{\hyperref[ref-0006]{1.0}}{\textgreater} & \textbf{Status:} \textbf{\textit{{\hyperref[ref-0005]{Final}}}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Available at:} \href{http://www.prace-project.eu}{http://www.prace-project.eu}} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{Software Tool:} Microsoft Word 2010} \\
\cline{2-2}\cline{3-3} & \multicolumn{2}{l}{\textbf{File(s):} d7.5\_4IP\_1.0.docx} \\
\multirow{3}{*}{\textbf{Authorship}}& \textbf{Written by:} & {\hyperref[ref-0007]{Victor Cameo Ponz,}}CINES \\
\cline{2-2}\cline{3-3} & \textbf{Contributors:} & Adem Tekin, ITU\par Alan Grey, EPCC\par Andrew Emerson, CINECA\par Andrew Sunderland, STFC\par Arno Proeme, EPCC\par Charles Moulinec, STFC\par Dimitris Dellis, GRNET\par Fiona Reid, EPCC\par Gabriel Hautreux, INRIA\par Jacob Finkenrath, CyI\par James Clark, STFC\par Janko Strassburg, BSC\par Jorge Rodriguez, BSC\par Martti Louhivuori, CSC\par Philippe Segers, GENCI\par Valeriu Codreanu, SURFSARA \\
\cline{2-2}\cline{3-3} & \textbf{Reviewed by:} & Filip Stanek, IT4I\par Thomas Eickermann, FZJ \\
\cline{2-2}\cline{3-3} & \textbf{Approved by:} & MB/TB \\

\end{tabularx}

\end{table}

\textbf{Document Status Sheet\label{ref-0010}}

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.24\linewidth-2\tabcolsep}
p{\dimexpr 0.24\linewidth-2\tabcolsep}
p{\dimexpr 0.24\linewidth-2\tabcolsep}
p{\dimexpr 0.29\linewidth-2\tabcolsep}}
\textbf{Version} & \textbf{Date} & \textbf{Status} & \textbf{Comments} \\
0.1 & $13/03/2017$ & Draft & First revision \\
0.2 & $15/03/2017$ & Draft & Include remark of the first review + new figures \\
1.0 & $24/03/2017$ & Final version & Improved the application performance section \\

\end{tabularx}

\end{table}

\textbf{Document Keywords \label{ref-0011}}

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.24\linewidth-2\tabcolsep}
p{\dimexpr 0.76\linewidth-2\tabcolsep}}
\textbf{Keywords:} & PRACE, HPC, Research Infrastructure, Accelerators, GPU, Xeon Phi, Benchmark suite \\

\end{tabularx}

\end{table}

\textbf{Disclaimer}

This deliverable has been prepared by the responsible Work Package of the Project in accordance with the Consortium Agreement and the Grant Agreement n$^{\circ}$ {\hyperref[ref-0002]{EINFRA-653838}}. It solely reflects the opinion of the parties to such agreements on a collective basis in the context of the Project and to the extent foreseen in such agreements. Please note that even though all participants to the Project are members of PRACE AISBL, this deliverable has not been approved by the Council of PRACE AISBL and therefore does not emanate from it nor should it be considered to reflect PRACE AISBL's individual opinion.

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 1\linewidth-2\tabcolsep}}
\textbf{Copyright notices}\par {\textcopyright} 2016 PRACE Consortium Partners. All rights reserved. This document is a project document of the PRACE project. All contents are reserved by default and may not be disclosed to third parties without the written consent of the PRACE partners, except as mandated by the European Commission contract {\hyperref[ref-0002]{EINFRA-653838}} for reviewing and dissemination purposes. \par All trademarks and other rights on third party products mentioned in this document are acknowledged as own by the respective holders. \\

\end{tabularx}

\end{table}

\textbf{Table of Contents\label{ref-0012}}

\textbf{Project and Deliverable Information Sheet \pageref{ref-0008}}

\textbf{Document Control Sheet \pageref{ref-0009}}

\textbf{Document Status Sheet \pageref{ref-0010}}

\textbf{Document Keywords \pageref{ref-0011}}

\textbf{Table of Contents \pageref{ref-0012}}

\textbf{List of Figures \pageref{ref-0013}}

\textbf{List of Tables \pageref{ref-0014}}

\textbf{References and Applicable Documents \pageref{ref-0015}}

\textbf{List of Acronyms and Abbreviations \pageref{ref-0036}}

\textbf{List of Project Partner Acronyms \pageref{ref-0037}}

\textbf{Executive Summary \pageref{ref-0038}}

\textbf{1 Introduction \pageref{ref-0039}}

\textbf{2 Targeted architectures \pageref{ref-0041}}

\textbf{2.1 Co-processor description \pageref{ref-0042}}

\textbf{2.2 Systems description \pageref{ref-0045}}

\textit{2.2.1 Cartesius K40 \pageref{ref-0047}}

\textit{2.2.2 MareNostrum KNC \pageref{ref-0048}}

\textit{2.2.3 Ouessant P100 \pageref{ref-0049}}

\textit{2.2.4 Frioul KNL \pageref{ref-0050}}

\textbf{3 Benchmark suite description \pageref{ref-0052}}

\textbf{3.1 Alya \pageref{ref-0055}}

\textit{3.1.1 Code description \pageref{ref-0056}}

\textit{3.1.2 Test cases description \pageref{ref-0057}}

\textbf{3.2 Code\_Saturne \pageref{ref-0058}}

\textit{3.2.1 Code description \pageref{ref-0059}}

\textit{3.2.2 Test cases description \pageref{ref-0060}}

\textbf{3.3 CP2K \pageref{ref-0061}}

\textit{3.3.1 Code description \pageref{ref-0062}}

\textit{3.3.2 Test cases description \pageref{ref-0063}}

\textbf{3.4 GPAW \pageref{ref-0064}}

\textit{3.4.1 Code description \pageref{ref-0065}}

\textit{3.4.2 Test cases description \pageref{ref-0066}}

\textbf{3.5 GROMACS \pageref{ref-0067}}

\textit{3.5.1 Code description \pageref{ref-0068}}

\textit{3.5.2 Test cases description \pageref{ref-0069}}

\textbf{3.6 NAMD \pageref{ref-0070}}

\textit{3.6.1 Code description \pageref{ref-0071}}

\textit{3.6.2 Test cases description \pageref{ref-0072}}

\textbf{3.7 PFARM \pageref{ref-0073}}

\textit{3.7.1 Code description \pageref{ref-0074}}

\textit{3.7.2 Test cases description \pageref{ref-0075}}

\textbf{3.8 QCD \pageref{ref-0076}}

\textit{3.8.1 Code description \pageref{ref-0077}}

\textit{3.8.2 Test cases description \pageref{ref-0078}}

\textbf{3.9 Quantum Espresso \pageref{ref-0079}}

\textit{3.9.1 Code description \pageref{ref-0080}}

\textit{3.9.2 Test cases description \pageref{ref-0081}}

\textbf{3.10 Synthetic benchmarks -- SHOC \pageref{ref-0082}}

\textit{3.10.1 Code description \pageref{ref-0083}}

\textit{3.10.2 Test cases description \pageref{ref-0084}}

\textbf{3.11 SPECFEM3D \pageref{ref-0085}}

\textit{3.11.1 Test cases definition \pageref{ref-0086}}

\textbf{4 Applications performances \pageref{ref-0088}}

\textbf{4.1 Alya \pageref{ref-0089}}

\textbf{4.2 Code\_Saturne \pageref{ref-0094}}

\textbf{4.3 CP2K \pageref{ref-0101}}

\textbf{4.4 GPAW \pageref{ref-0104}}

\textbf{4.5 GROMACS \pageref{ref-0110}}

\textbf{4.6 NAMD \pageref{ref-0113}}

\textbf{4.7 PFARM \pageref{ref-0116}}

\textbf{4.8 QCD \pageref{ref-0123}}

\textit{4.8.1 First implementation \pageref{ref-0124}}

\textit{4.8.2 Second implementation \pageref{ref-0131}}

\textbf{4.9 Quantum Espresso \pageref{ref-0142}}

\textbf{4.10 Synthetic benchmarks (SHOC) \pageref{ref-0152}}

\textbf{4.11 SPECFEM3D \pageref{ref-0155}}

\textbf{5 Conclusion and future work \pageref{ref-0158}}

\textbf{List of Figures\label{ref-0013}}

{\hyperref[ref-0090]{Figure 1 Shows the matrix construction part of Alya that is parallelised with OpenMP and benefits significantly from the many cores available on KNL.}} {\hyperref[ref-0090]{ }}

{\hyperref[ref-0091]{Figure 2 Demonstrates the scalability of the code. As expected Haswell cores with K80 GPU are high-performing while the KNL port is currently being optimized further.}} {\hyperref[ref-0091]{ }}

{\hyperref[ref-0093]{Figure 3 Best performance is achieved with GPU in combination with powerful CPU cores. Single thread performance has a big impact on the speedup, both threading and vectorization are employed for additional performance.}} {\hyperref[ref-0093]{ }}

{\hyperref[ref-0096]{Figure 4 Code_Saturne's performance on KNL. AMG is used as a solver in V4.2.2.}} {\hyperref[ref-0096]{ }}

{\hyperref[ref-0103]{Figure 5 Test case 1 of CP2K on the ARCHER cluster}} {\hyperref[ref-0103]{ }}

{\hyperref[ref-0109]{Figure 6 Relative performance (to / t) of GPAW is shown for parallel jobs using an increasing number of CPU (blue) or Xeon Phi KNC (red). Single CPU SCF-cycle runtime (to) was used as the baseline for the normalisation. Ideal scaling is shown as a linear dashed line for comparison. Case 1 (Carbon Nanotube) is shown with square markers and Case 2 (Copper Filament) is shown with round markers.}} {\hyperref[ref-0109]{ }}

{\hyperref[ref-0111]{Figure 7 Scalability for GROMACS test case GluCL Ion Channel}} {\hyperref[ref-0111]{ }}

{\hyperref[ref-0112]{Figure 8 Scalability for GROMACS test case Lignocellulose}} {\hyperref[ref-0112]{ }}

{\hyperref[ref-0114]{Figure 9 Scalability for NAMD test case STMV.8M}} {\hyperref[ref-0114]{ }}

{\hyperref[ref-0115]{Figure 10 Scalability for NAMD test case STMV.28M}} {\hyperref[ref-0115]{ }}

{\hyperref[ref-0118]{Figure 11 Eigensolver performance on KNL and GPU}} {\hyperref[ref-0118]{ }}

{\hyperref[ref-0126]{Figure 12 Small test case results for QCD, first implementation}} {\hyperref[ref-0126]{ }}

{\hyperref[ref-0128]{Figure 13 Large test case results for QCD, first implementation}} {\hyperref[ref-0128]{ }}

{\hyperref[ref-0130]{Figure 14 shows the time taken by the full MILC 64x64x64x8 test cases on traditional CPU, Intel Knights Landing Xeon Phi and NVIDIA P100 (Pascal) GPU architectures.}} {\hyperref[ref-0130]{ }}

{\hyperref[ref-0133]{Figure 15 Result of second implementation of QCD on K40m GPU}} {\hyperref[ref-0133]{ }}

{\hyperref[ref-0135]{Figure 16 Result of second implementation of QCD on P100 GPU}} {\hyperref[ref-0135]{ }}

{\hyperref[ref-0137]{Figure 17 Result of second implementation of QCD on P100 GPU on larger test case}} {\hyperref[ref-0137]{ }}

{\hyperref[ref-0139]{Figure 18 Result of second implementation of QCD on KNC}} {\hyperref[ref-0139]{ }}

{\hyperref[ref-0141]{Figure 19 Result of second implementation of QCD on KNL}} {\hyperref[ref-0141]{ }}

{\hyperref[ref-0144]{Figure 20 Scalability of Quantum Espresso on GPU for test case 1}} {\hyperref[ref-0144]{ }}

{\hyperref[ref-0146]{Figure 21 Scalability of Quantum Espresso on GPU for test case 2}} {\hyperref[ref-0146]{ }}

{\hyperref[ref-0148]{Figure 22 Scalability of Quantum Espresso on KNL for test case 1}} {\hyperref[ref-0148]{ }}

{\hyperref[ref-0150]{Figure 23 Quantum Espresso - KNL vs BDW vs BGQ (at scale)}} {\hyperref[ref-0150]{ }}

\textbf{List of Tables\label{ref-0014}}

Table 1 Main co-processors specifications \pageref{ref-0044}

Table 2 Codes and corresponding APIs available (in green) \pageref{ref-0054}

Table 3 Performance of Code\_Saturne + PETSc on 1 node of the POWER8 clusters. Comparison between 2 different nodes, using different types of CPU and GPU. PETSc is built on LAPACK. The speedup is computed at the ratio between the time to solution on the CPU for a given number of MPI tasks and the time to solution on the CPU/GPU for the same number of MPI tasks. \pageref{ref-0098}

Table 4 Performance of Code\_Saturne and PETSc on 1 node of KNL. PETSc is built on the MKL library \pageref{ref-0100}

Table 5 GPAW runtimes (in seconds) for the smaller benchmark (Carbon Nanotube) measured on several architectures when using n sockets (i.e. processors or accelerators). \pageref{ref-0106}

Table 6 GPAW runtimes (in seconds) for the larger benchmark (Copper Filament) measured on several architectures when using n sockets (i.e. processors or accelerators). *Due to memory limitations on the GPU the grid spacing was increased from 0.22 to 0.28 to have a sparser grid. To account for this in the comparison, the K40 and K80 runtimes have been scaled up using a corresponding CPU runtime as a yardstick (scaling factor q=2.1132). \pageref{ref-0108}

Table 7 Overall EXDIG runtime performance on various accelerators (runtime, secs) \pageref{ref-0120}

Table 8 Overall EXDIG runtime parallel performance using MPI-GPU version \pageref{ref-0122}

Table 9 Synthetic benchmarks results on GPU and Xeon Phi \pageref{ref-0154}

Table 10 SPECFEM 3D GLOBE results (run time in second) \pageref{ref-0156}

\textbf{References and Applicable Documents\label{ref-0015}}

\begin{enumerate}[1]

\item \href{http://www.prace-ri.eu}{\label{ref-0016}http://www.prace-ri.eu} 

\item The Unified European Application Benchmark Suite -- \href{http://www.prace-ri.eu/ueabs/}{http://www.prace-ri.eu/ueabs/}\label{ref-0017}

\item D7.4 Unified European Applications Benchmark Suite -- Mark Bull et al. -- 2013\label{ref-0018}

\item \href{http://www.nvidia.com/object/quadro-design-and-manufacturing.html}{\label{ref-0019}http://www.nvidia.com/object/quadro-design-and-manufacturing.html}

\item \href{https://userinfo.surfsara.nl/systems/cartesius/description}{https://userinfo.surfsara.nl/systems/cartesius/description}\label{ref-0020}

\item MareNostrum III User's Guide Barcelona Supercomputing Center -- \href{https://www.bsc.es/support/MareNostrum3-ug.pdf}{https://www.bsc.es/support/MareNostrum3-ug.pdf}\label{ref-0021}

\item \href{http://www.idris.fr/eng/ouessant/}{http://www.idris.fr/eng/ouessant/}\label{ref-0022}

\item PFARM reference -- \href{https://hpcforge.org/plugins/mediawiki/wiki/pracewp8/images/3/34/Pfarm_long_lug.pdf}{https://hpcforge.org/plugins/mediawiki/wiki/pracewp8/images/3/34/Pfarm\_long\_lug.pdf}\label{ref-0023}

\item Solvent-Driven Preferential Association of Lignin with Regions of Crystalline Cellulose in Molecular Dynamics Simulation -- Benjamin Lindner et al. -- Biomacromolecules, 2013\label{ref-0024}

\item NAMD website -- \href{http://www.ks.uiuc.edu/Research/namd/}{http://www.ks.uiuc.edu/Research/namd/}\label{ref-0025}

\item SHOC source repository -- \href{https://github.com/vetter/shoc}{https://github.com/vetter/shoc}\label{ref-0026}

\item Parallelizing the QUDA Library for Multi-GPU Calculations in Lattice Quantum Chromodynamics -- R. Babbich, M. Clark and B. Joo -- SC 10 (Supercomputing 2010)\label{ref-0027}

\item Lattice QCD on Intel Xeon Phi -- B. Joo, D. D. Kalamkar, K. Vaidyanathan, M. Smelyanskiy, K. Pamnany, V. W. Lee, P. Dubey, W. Watson III -- International Supercomputing Conference (ISC'13), 2013\label{ref-0028}

\item Extension of fractional step techniques for incompressible flows: The preconditioned Orthomin(1) for the pressure Schur complement -- G. Houzeaux, R. Aubry, and M. V\'{a}zquez -- Computers \& Fluids, 44:297-313, 2011\label{ref-0029}

\item MIMD Lattice Computation (MILC) Collaboration -- \href{http://physics.indiana.edu/~sg/milc.html}{http://physics.indiana.edu/\textasciitilde{}sg/milc.html}\label{ref-0030}

\item targetDP -- \href{https://ccpforge.cse.rl.ac.uk/svn/ludwig/trunk/targetDP/README}{https://ccpforge.cse.rl.ac.uk/svn/ludwig/trunk/targetDP/README}\label{ref-0031}

\item QUDA: A library for QCD on GPU -- \href{https://lattice.github.io/quda/}{https://lattice.github.io/quda/}\label{ref-0032}

\item QPhiX, QCD for Intel Xeon Phi and Xeon processors -- \href{http://jeffersonlab.github.io/qphix/}{http://jeffersonlab.github.io/qphix/}\label{ref-0033}

\item KNC MaxFlops issue (both SP and DP) -- \href{https://github.com/vetter/shoc/issues/37}{https://github.com/vetter/shoc/issues/37}\label{ref-0034}

\item \label{ref-0035}KNC SpMV issue -- https://github.com/vetter/shoc/issues/24, https://github.com/vetter/shoc/issues/23.

\end{enumerate}

\textbf{List of Acronyms and Abbreviations\label{ref-0036}}

\begin{description}
\item[aisbl]Association International Sans But Lucratif \newline
 (legal form of the PRACE-RI)

\item[BCO]Benchmark Code Owner 

\end{description}

CoE Center of Excellence 

\begin{description}
\item[CPU]Central Processing Unit

\item[CUDA]Compute Unified Device Architecture (NVIDIA)

\item[DARPA]Defense Advanced Research Projects Agency

\item[DEISA]Distributed European Infrastructure for Supercomputing Applications EU project by leading national HPC centres

\end{description}

DoA Description of Action (formerly known as DoW)

\begin{description}
\item[EC]European Commission

\item[EESI]European Exascale Software Initiative

\end{description}

EoI Expression of Interest

\begin{description}
\item[	ESFRI]European Strategy Forum on Research Infrastructures 

\item[GB]Giga (= 2$^{\mathrm{30}}$ \textasciitilde{} 10$^{\mathrm{9}}$) Bytes (= 8 bits), also GByte

\end{description}

Gb/s Giga (= 10$^{\mathrm{9}}$) bits per second, also Gbit/s

GB/s Giga (= 10$^{\mathrm{9}}$) Bytes (= 8 bits) per second, also GByte/s

\begin{description}
\item[	G\'{E}ANT]Collaboration between National Research and Education Networks to build a multi-gigabit pan-European network. The current EC-funded project as of 2015 is GN4.

\item[GFlop/s]Giga (= 10$^{\mathrm{9}}$) Floating point operations (usually in 64-bit, i.e. DP) per second, also GF/s

\end{description}

GHz Giga (= 10$^{\mathrm{9}}$) Hertz, frequency =10$^{\mathrm{9}}$ periods or clock cycles per second

\begin{description}
\item[GPU]Graphic Processing Unit

\item[	HET]High Performance Computing in Europe Taskforce. Taskforce by representatives from European HPC community to shape the European HPC Research Infrastructure. Produced the scientific case and valuable groundwork for the PRACE project.

\item[HMM]Hidden Markov Model

\item[HPC]High Performance Computing; Computing at a high performance level at any given time; often used synonym with Supercomputing

\item[HPL]High Performance LINPACK 

\item[	ISC]International Supercomputing Conference; European equivalent to the US based SCxx conference. Held annually in Germany.

\item[KB]Kilo (= 2$^{\mathrm{10}}$ \textasciitilde{}10$^{\mathrm{3}}$) Bytes (= 8 bits), also KByte

\item[LINPACK]Software library for Linear Algebra

\item[MB]Management Board (highest decision making body of the project)

\item[MB]Mega (= 2$^{\mathrm{20}}$ \textasciitilde{} 10$^{\mathrm{6}}$) Bytes (= 8 bits), also MByte

\end{description}

MB/s Mega (= 10$^{\mathrm{6}}$) Bytes (= 8 bits) per second, also MByte/s

MFlop/sMega (= 10$^{\mathrm{6}}$) Floating point operations (usually in 64-bit, i.e. DP) per second, also MF/s

MooC Massively open online Course

MoU Memorandum of Understanding

\begin{description}
\item[MPI]Message Passing Interface

\item[	NDA]Non-Disclosure Agreement. Typically signed between vendors and customers working together on products prior to their general availability or announcement.

\item[	PA]Preparatory Access (to PRACE resources)

\item[	PATC]PRACE Advanced Training Centres

\item[PRACE]Partnership for Advanced Computing in Europe; Project Acronym

\item[PRACE 2]The upcoming next phase of the PRACE Research Infrastructure following the initial five year period.

\item[PRIDE]Project Information and Dissemination Event

\item[RI]Research Infrastructure

\item[TB]Technical Board (group of Work Package leaders)

\item[TB]Tera (= 240 \textasciitilde{} 1012) Bytes (= 8 bits), also TByte

\item[TCO]Total Cost of Ownership. Includes recurring costs (e.g. personnel, power, cooling, maintenance) in addition to the purchase cost.

\item[TDP]Thermal Design Power

\item[TFlop/s]Tera (= 1012) Floating-point operations (usually in 64-bit, i.e. DP) per second, also TF/s

\item[Tier-0]Denotes the apex of a conceptual pyramid of HPC systems. In this context the Supercomputing Research Infrastructure would host the Tier-0 systems; national or topical HPC centres would constitute Tier-1

\item[UNICORE]Uniform Interface to Computing Resources. Grid software for seamless access to distributed resources.

\end{description}

\textbf{List of Project Partner Acronyms\label{ref-0037}}

\begin{description}
\item[	BADW-LRZ]Leibniz-Rechenzentrum der Bayerischen Akademie der Wissenschaften, Germany (3$^{\mathrm{rd}}$ Party to GCS)

\item[	BILKENT]Bilkent University, Turkey (3$^{\mathrm{rd}}$ Party to UYBHM)

\item[	BSC]Barcelona Supercomputing Center - Centro Nacional de Supercomputacion, Spain 

\item[	CaSToRC]Computation-based Science and Technology Research Center, Cyprus

\item[	CCSAS]Computing Centre of the Slovak Academy of Sciences, Slovakia

\item[	CEA]Commissariat \`{a} l'Energie Atomique et aux Energies Alternatives, France (3$^{\mathrm{ rd}}$ Party to GENCI)

\item[	CESGA]Fundacion Publica Gallega Centro Tecnol\'{o}gico de Supercomputaci\'{o}n de Galicia, Spain, (3$^{\mathrm{rd}}$ Party to BSC)

\item[	CINECA]CINECA Consorzio Interuniversitario, Italy

\item[	CINES]Centre Informatique National de l'Enseignement Sup\'{e}rieur, France (3$^{\mathrm{ rd}}$ Party to GENCI)

\item[	CNRS]Centre National de la Recherche Scientifique, France (3$^{\mathrm{ rd}}$ Party to GENCI)

\item[	CSC]CSC Scientific Computing Ltd., Finland

\item[	CSIC]Spanish Council for Scientific Research (3$^{\mathrm{rd}}$ Party to BSC)

\item[	CYFRONET]Academic Computing Centre CYFRONET AGH, Poland (3rd party to PNSC)

\item[	EPCC]EPCC at The University of Edinburgh, UK 

\item[	ETHZurich (CSCS)]Eidgen\"{o}ssische Technische Hochschule Z\"{u}rich -- CSCS, Switzerland

\item[	FIS]FACULTY OF INFORMATION STUDIES, Slovenia (3$^{\mathrm{rd}}$ Party to ULFME)

\item[	GCS]Gauss Centre for Supercomputing e.V.

\item[	GENCI]Grand Equipement National de Calcul Intensiv, France

\item[	GRNET]Greek Research and Technology Network, Greece

\item[	INRIA]Institut National de Recherche en Informatique et Automatique, France (3$^{\mathrm{ rd}}$ Party to GENCI)

\item[	IST]Instituto Superior T\'{e}cnico, Portugal (3rd Party to UC-LCA)

\item[	IUCC]INTER UNIVERSITY COMPUTATION CENTRE, Israel

\item[	JKU]Institut fuer Graphische und Parallele Datenverarbeitung der Johannes Kepler Universitaet Linz, Austria

\item[	JUELICH]Forschungszentrum Juelich GmbH, Germany

\item[	KTH]Royal Institute of Technology, Sweden (3$^{\mathrm{ rd}}$ Party to SNIC)

\item[	LiU]Linkoping University, Sweden (3$^{\mathrm{ rd}}$ Party to SNIC)

\item[	NCSA]NATIONAL CENTRE FOR SUPERCOMPUTING APPLICATIONS, Bulgaria

\item[	NIIF]National Information Infrastructure Development Institute, Hungary

\item[	NTNU]The Norwegian University of Science and Technology, Norway (3$^{\mathrm{rd}}$ Party to SIGMA)

\item[	NUI-Galway]National University of Ireland Galway, Ireland

\item[	PRACE]Partnership for Advanced Computing in Europe aisbl, Belgium

\item[	PSNC]Poznan Supercomputing and Networking Center, Poland

\item[	RISCSW]RISC Software GmbH

\item[	RZG]Max Planck Gesellschaft zur F\"{o}rderung der Wissenschaften e.V., Germany (3$^{\mathrm{ rd}}$ Party to GCS)

\item[	SIGMA2]UNINETT Sigma2 AS, Norway

\item[	SNIC]Swedish National Infrastructure for Computing (within the Swedish Science Council), Sweden

\item[	STFC]Science and Technology Facilities Council, UK (3$^{\mathrm{rd}}$ Party to EPSRC)

\item[	SURFsara]Dutch national high-performance computing and e-Science support center, part of the SURF cooperative, Netherlands

\item[	UC-LCA]Universidade de Coimbra, Labotat\'{o}rio de Computa\c{c}\~{a}o Avan\c{c}ada, Portugal

\item[	UCPH]K\o{}benhavns Universitet, Denmark

\item[	UHEM]Istanbul Technical University, Ayazaga Campus, Turkey

\item[	UiO]University of Oslo, Norway (3$^{\mathrm{rd}}$ Party to SIGMA)

\item[	ULFME]UNIVERZA V LJUBLJANI, Slovenia

\item[	UmU]Umea University, Sweden (3$^{\mathrm{ rd}}$ Party to SNIC)

\item[	UnivEvora]Universidade de \'{E}vora, Portugal (3rd Party to UC-LCA)

\item[	UPC]Universitat Polit\`{e}cnica de Catalunya, Spain (3rd Party to BSC)

\item[	UPM/CeSViMa]Madrid Supercomputing and Visualization Center, Spain (3$^{\mathrm{rd}}$ Party to BSC)

\item[	USTUTT-HLRS]Universitaet Stuttgart -- HLRS, Germany (3rd Party to GCS)

\item[	VSB-TUO]VYSOKA SKOLA BANSKA - TECHNICKA UNIVERZITA OSTRAVA, Czech Republic

\item[	WCNS]Politechnika Wroclawska, Poland (3rd party to PNSC)

\end{description}

\textbf{Executive Summary\label{ref-0038}}

This document describes an accelerator benchmark suite, a set of 11 codes that includes 1 synthetic benchmark and 10 commonly used applications. The key focus of this task has been exploiting accelerators or co-processors to improve the performance of real applications. It aims at providing a set of scalable, currently relevant and publically available codes and datasets.

This work has been undertaken by Task7.2B "Accelerator Benchmarks" in the PRACE Fourth Implementation Phase (PRACE-4IP) project.

Most of the selected application are a subset of the Unified European Applications Benchmark Suite (UEABS) {\hyperref[ref-0017]{[2]}}{\hyperref[ref-0018]{[3]}}. One application and a synthetic benchmark have been added.

As a result, selected codes are: Alya, Code\_Saturne, CP2K, GROMACS, GPAW, NAMD, PFARM, QCD, Quantum Espresso, SHOC and SPECFEM3D.

For each code either two or more test case datasets have been selected. These are described in this document, along with a brief introduction to the application codes themselves. For each code, some sample results are presented, from first run on leading edge systems and prototypes.

\section{1 Introduction\label{ref-0039}}

The work produced within this task is an extension of the UEABS for accelerators. This document will cover each code, presenting the code as well as the test cases defined for the benchmarks and the first results that have been recorded on various accelerator systems.

As the UEABS, this suite aims to present results for many scientific fields that can use HPC accelerated resources. Hence, it will help the European scientific communities to decide in terms of infrastructures they could buy in a near future. We focus on Intel Xeon Phi coprocessors and NVIDIA GPU cards for benchmarking as they are the two most wide-spread accelerated resources available now.

Section {\hyperref[ref-0040]{2}} will present both types of accelerator systems, Xeon Phi and GPU card along with architecture examples. Section {\hyperref[ref-0051]{3}} gives a description of each of the selected applications, together with the test case datasets while section {\hyperref[ref-0087]{4}} presents some sample results. Section {\hyperref[ref-0157]{5}} outlines further work on, and using, the suite.

\section{2 Targeted architectures\label{ref-0040}\label{ref-0041}}

This suite is targeting accelerator cards, more specifically the Intel Xeon Phi and NVIDIA GPU architecture. This section will quickly describe them and will present the 4 machines, the benchmarks ran on.

\subsection{2.1 Co-processor description\label{ref-0042}}

Scientific computing using co-processors has gained popularity in recent years. First the utility of GPU has been demonstrated and evaluated in several application domains {\hyperref[ref-0019]{[4]}}. As a response to NVIDIA's supremacy in this field, Intel designed Xeon Phi cards.

Architectures and programming models of co-processors may differ from CPU and vary among different co-processor types. The main challenges are the high-level parallelism ability required from software and the fact that code may have to be offloaded to the accelerator card.

The {\hyperref[ref-0043]{Table 1}} enlightens this fact:

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.24\linewidth-2\tabcolsep}
p{\dimexpr 0.18\linewidth-2\tabcolsep}
p{\dimexpr 0.2\linewidth-2\tabcolsep}
p{\dimexpr 0.2\linewidth-2\tabcolsep}
p{\dimexpr 0.19\linewidth-2\tabcolsep}}
 & \multicolumn{2}{l}{Intel Xeon Phi} & \multicolumn{2}{l}{NVIDIA GPU} \\
 & 5110P (KNC) & 7250 (KNL) & K40m & P100 \\
public availability date & Nov-12 & Jun-16 & Jun-13 & May-16 \\
theoretical peak perf & 1,011 GF/s & 3,046 GF/s & 1,430 GF/s & 5,300 GF/s \\
offload required & possible & not possible & required & required \\
max number of thread/cuda cores & 240 & 272 & 2880 & 3584 \\

\end{tabularx}

\end{table}

\textbf{Table 1 Main co-processors specifications\label{ref-0043}\label{ref-0044}}

\subsection{2.2 Systems description\label{ref-0045}}

The benchmark suite has been officially granted access to 4 different machines hosted by PRACE partners. Most results presented in this paper were obtained on these machines but some of the simulation has run on similar ones. This section will cover specifications of the sub mentioned 4 official systems while the few other ones will be presented along with concerned results.

As it can be noticed on the previous section, leading edge architectures have been available quite recently and some code couldn't run on it yet. Results will be completed in a near future and will be delivered with an update of the benchmark suite. Still, presented performances are a good indicator about potential efficiency of codes on both Xeon Phi and NVIDIA GPU platforms.

As for the future, the PRACE-3IP PCP is in its third and last phase and will be a good candidate to provide access to bigger machines. The following suppliers had been awarded with a contract: ATOS/Bull SAS (France), E4 Computer Engineering (Italy) and Maxeler Technologies (UK), providing pilots using Xeon Phi, OPENPower and FPGA technologies. During this final phase, which started in October 2016, the contractors will have to deploy pilot system with a compute capability of around 1 PFlop/s, to demonstrate technology readiness of the proposed solution and the progress in terms of energy efficiency, using high frequency monitoring designed for this purpose. These results will be evaluated on a subset of applications from UEABS (NEMO, SPECFEM3D, QuantumEspresso, BQCD). The access to these systems is foreseen to be open to PRACE partners, with a special interest for the 4IP-WP7 task on accelerated Benchmarks.

\subsubsection{\raisebox{-0pt}{2.2.1} Cartesius K40\label{ref-0046}\label{ref-0047}}

The SURFsara institute in The Netherlands granted access to Cartesius which has a GPU island (installed May 2014) with following specifications {\hyperref[ref-0020]{[5]}}:

\begin{itemize}
\item 66 Bullx B515 GPU accelerated nodes

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item 2x 8-core 2.5 GHz Intel Xeon E5-2450 v2 (Ivy Bridge) CPU/node

\item 2x NVIDIA Tesla K40m GPU/node

\item 96 GB/node, DDR3-1600 RAM

\end{enumerate}

\item Total theoretical peak performance (Ivy Bridge + K40m) 1,056 cores + 132 GPU: 210 TF/s

\end{itemize}
The interconnect has a fully non-blocking fat-tree topology. Every node has two ConnectX-3 InfiniBand FDR adapters: one per GPU.

\subsubsection{\raisebox{-0pt}{2.2.2} MareNostrum KNC\label{ref-0048}}

The Barcelona Supercomputing Center (BSC) in Spain granted access to MareNostrum III which features KNC nodes (upgrade June 2013). Here's the description of this partition {\hyperref[ref-0021]{[6]}}:

\begin{itemize}
\item 42 hybrid nodes containing:

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item 1x Sandy-Bridge-EP (2 x 8 cores) host processors E5-2670 

\item 8x 8G DDR3--1600 DIMMs (4GB/core), total: 64GB/node

\item 2x Xeon Phi 5110P accelerators

\end{enumerate}

\item Interconnection networks:

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item Infiniband Mellanox FDR10: High bandwidth network used by parallel applications communications (MPI)

\item Gigabit Ethernet: 10GbitEthernet network used by the GPFS Filesystem.

\end{enumerate}

\subsubsection{\raisebox{-0pt}{2.2.3} Ouessant P100\label{ref-0049}}

\end{itemize}
GENCI granted access to the Ouessant prototype at IDRIS in France (installed September 2016). It is composed of 12 IBM Minsky compute nodes with each containing {\hyperref[ref-0022]{[7]}}:

\begin{itemize}
\item Compute nodes

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item POWER8+ sockets, 10 cores, 8 threads per core (or 160 threads per node)

\item 128 GB of DDR4 memory (bandwidth {\textgreater} 9 GB/s per core)

\item 4 NVIDIA's new generation Pascal P100 GPU, 16 GB of HBM2 memory

\end{enumerate}

\item Interconnect

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item 4 NVLink interconnects (40GB/s of bi-directional bandwidth per interconnect); each GPU card is connected to a CPU with 2 NVLink interconnects and another GPU with 2 interconnects remaining

\item A Mellanox EDR InfiniBand CAPI interconnect network (1 interconnect per node)

\end{enumerate}

\subsubsection{\raisebox{-0pt}{2.2.4} Frioul KNL\label{ref-0050}}

\end{itemize}
GENCI also granted access to the Frioul prototype at CINES in France (installed December 2016). It is composed of 48 Intel KNL compute nodes each containing:

\begin{itemize}
\item Compute nodes

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item 7250 KNL, 68 cores, 4 threads per cores

\item 192GB of DDR4 memory

\item 16GB of MCDRAM

\end{enumerate}

\item Interconnect:

\begin{enumerate}[a]
\setcounter{enumi}{14}

\item A Mellanox EDR 4x InfiniBand

\end{enumerate}

\end{itemize}
\section{3 Benchmark suite description\label{ref-0051}\label{ref-0052}}

This part will cover each code, presenting the interest for the scientific community as well as the test cases defined for the benchmarks.

As an extension to the EUABS, most codes presented in this suite are included in the latter. Exceptions are PFARM which comes from PRACE-2IP {\hyperref[ref-0023]{[8]}} and SHOC {\hyperref[ref-0026]{[11]}} a synthetic benchmark suite.

\includegraphics[width=0.5\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image2.emf}\includegraphics[width=0.5\textwidth]{embeddings/Microsoft_Excel_Worksheet1.xlsx}

\textbf{Table 2 Codes and corresponding APIs available (in green)\label{ref-0053}\label{ref-0054}}

{\hyperref[ref-0053]{Table 2}} lists the codes that will be presented in the next sections as well as their implementations available. It should be noted that OpenMP can be used with the Intel Xeon Phi architecture while CUDA is used for NVidia GPU cards. OpenCL has been considered as a third alternative that can be used on both architectures. It has been available on the first generation of Xeon Phi (KNC) but has not been ported to the second one (KNL). SHOC is the only code that is impacted, this problem is addressed in section {\hyperref[ref-0151]{4.10}}.

\subsection{3.1 Alya\label{ref-0055}}

Alya is a high performance computational mechanics code that can solve different coupled mechanics problems: incompressible/compressible flows, solid mechanics, chemistry, excitable media, heat transfer and Lagrangian particle transport. It is one single code. There are no particular parallel or individual platform versions. Modules, services and kernels can be compiled individually and used a la carte. The main discretisation technique employed in Alya is based on the variational multiscale finite element method to assemble the governing equations into Algebraic systems. These systems can be solved using solvers like GMRES, Deflated Conjugate Gradient, pipelined CG together with preconditioners like SSOR, Restricted Additive Schwarz, etc. The coupling between physics solved in different computational domains (like fluid-structure interactions) is carried out in a multi-code way, using different instances of the same executable. Asynchronous coupling can be achieved in the same way in order to transport Lagrangian particles.

\subsubsection{\raisebox{-0pt}{3.1.1} Code description\label{ref-0056}}

The code is parallelised with MPI and OpenMP. Two OpenMP strategies are available, without and with a colouring strategy to avoid ATOMICs during the assembly step. A CUDA version is also available for the different solvers. Alya has been also compiled for MIC (Intel Xeon Phi).

Alya is written in Fortran 1995 and the incompressible fluid module, present in the benchmark suite, is freely available. This module solves the Navier-Stokes equations using an Orthomin(1) {\hyperref[ref-0029]{[14]}} method for the pressure Schur complement. This method is an algebraic split strategy which converges to the monolithic solution. At each linearisation step, the momentum is solved twice and the continuity equation is solved once or twice depending whether the momentum preserving or the continuity preserving algorithm is selected.

\subsubsection{\raisebox{-0pt}{3.1.2} Test cases description\label{ref-0057}}

\textit{Cavity-hexaedra elements (10M elements)}

This test is the classical lid-driven cavity. The problem geometry is a cube of dimensions 1x1x1. The fluid properties are density=1.0 and viscosity=0.01. Dirichlet boundary conditions are applied on all sides, with three no-slip walls and one moving wall with velocity equal to 1.0, which corresponds to a Reynolds number of 100. The Reynolds number is low so the regime is laminar and turbulence modelling is not necessary. The domain is discretised into 9800344 hexaedra elements. The solvers are the GMRES method for the momentum equations and the Deflated Conjugate Gradient to solve the continuity equation. This test case can be run using pure MPI parallelisation or the hybrid MPI/OpenMP strategy.

\textit{Cavity-hexaedra elements (30M elements)}

This is the same cavity test as before but with 30M of elements. Note that a mesh multiplication strategy enables one to multiply the number of elements by powers of 8, by simply activating the corresponding option in the ker.dat file.

\textit{Cavity-hexaedra elements-GPU version (10M elements)}

This is the same test as Test case 1, but using the pure MPI parallelisation strategy with acceleration of the algebraic solvers using GPU.

\subsection{3.2 Code\_Saturne\label{ref-0058}}

Code\_Saturne is a CFD software package developed by EDF R\&D since 1997 and open-source since 2007. The Navier-Stokes equations are discretised following a finite volume method approach. The code can handle any type of mesh built with any type of cell/grid structure. Incompressible and compressible flows can be simulated, with or without heat transfer, and a range of turbulence models is available. The code can also be coupled with itself or other software to model some multi-physics problems (fluid-structure, fluid-conjugate heat transfer, for instance).

\subsubsection{\raisebox{-0pt}{3.2.1} Code description\label{ref-0059}}

Parallelism is handled by distributing the domain over the processors (several partitioning tools are available, either internally, i.e. SFC Hilbert and Morton, or through external libraries, i.e. METIS Serial, ParMETIS, Scotch Serial, PT-SCOTCH. Communications between subdomains are handled by MPI. Hybrid parallelism using MPI/OpenMP has recently been optimised for improved multicore performance.

For incompressible simulations, most of the time is spent during the computation of the pressure through Poisson equations. The matrices are very sparse. PETSc has recently been linked to the code to offer alternatives to the internal solvers to compute the pressure. The developer's version of PETSc supports CUDA and is used in this benchmark suite.

Code\_Saturne is written in C, F95 and Python. It is freely available under the GPL license.

\subsubsection{\raisebox{-0pt}{3.2.2} Test cases description\label{ref-0060}}

Two test cases are dealt with, the former with a mesh made of hexahedral cells and the latter with a mesh made of tetrahedral cells. Both configurations are meant for incompressible laminar flows. The first test case is run on KNL in order to test the performance of the code always completely filling up a node using 64 MPI tasks and then either 1, 2, 4 OpenMP threads, or 1, 2, 4 extra MPI tasks to investigate the effect of hyper-threading. In this case, the pressure is computed using the code's native Algebraic Multigrid (AMG) algorithm as a solver. The second test case is run on KNL and GPU. In this configuration, the pressure equation is solved using the conjugate gradient (CG) algorithm from the PETSc library (the version of PETSc is the developer's version which supports GPU) and tests are run on KNL as well as on CPU+GPU. PETSc is built with the CUSP library and the CUSP format is used.

Note that computing the pressure using a CG algorithm has always been slower than using the native AMG algorithm, when using Code\_Saturne. The second test is then meant to compare the current results obtained on KNL and GPU using CG only, and not to compare CG and AMG time to solution.

\textit{Flow in a 3-D lid-driven cavity (tetrahedral cells)}

The geometry is very simple, i.e. a cube, but the mesh is built using tetrahedral cells only. The Reynolds number is set to 100, and symmetry boundary conditions are applied in the spanwise direction. The case is modular and the mesh size can easily been varied. The largest mesh has about 13 million cells and is used to get some first comparisons using Code\_Saturne linked to the developer's PETSc library, in order to get use of the GPU.

\textit{3-D Taylor-Green vortex flow (hexahedral cells)}

The Taylor-Green vortex flow is traditionally used to assess the accuracy of CFD code numerical schemes. Periodicity is used in the 3 directions. The total kinetic energy (integral of the velocity) and enstrophy (integral of the vorticity) evolutions as a function of the time are looked at. Code\_Saturne is set for 2nd order time and spatial schemes. The mesh size is 2563 cells.

\subsection{3.3 CP2K\label{ref-0061}}

CP2K is a quantum chemistry and solid state physics software package that can perform atomistic simulations of solid state, liquid, molecular, periodic, material, crystal, and biological systems. It can perform molecular dynamics, metadynamics, Quantum Monte Carlo, Ehrenfest dynamics, vibrational analysis, core level spectroscopy, energy minimisation, and transition state optimisation using NEB or dimer method.

CP2K provides a general framework for different modelling methods such as density functional theory (DFT) using the mixed Gaussian and plane waves approaches (GPW) and Gaussian and Augmented Plane (GAPW). Supported theory levels include DFTB, LDA, GGA, MP2, RPA, semi-empirical methods (AM1, PM3, PM6, RM1, MNDO, {\ldots}), and classical force fields (AMBER, CHARMM, {\ldots}).

\subsubsection{\raisebox{-0pt}{3.3.1} Code description\label{ref-0062}}

Parallelisation is achieved using a combination of OpenMP-based multi-threading and MPI.

Offloading for accelerators is implemented through CUDA and OpenCL for GPU and through OpenMP for MIC (Intel Xeon Phi).

CP2K is written in Fortran 2003 and freely available under the GPL license.

\subsubsection{\raisebox{-0pt}{3.3.2} Test cases description\label{ref-0063}}

\textit{LiH-HFX}

This is a single-point energy calculation for a particular configuration of a 216 atom Lithium Hydride crystal with 432 electrons in a 12.3 \AA{}$^{\mathrm{3}}$ (Angstroms cubed) cell. The calculation is performed using a DFT algorithm with GAPW under the hybrid Hartree-Fock exchange (HFX) approximation. These types of calculations are generally around one hundred times the computational cost of a standard local DFT calculation, although the cost of the latter can be reduced by using the Auxiliary Density Matrix Method (ADMM). Using OpenMP is of particular benefit here as the HFX implementation requires a large amount of memory to store partial integrals. By using several threads, fewer MPI processes share the available memory on the node and thus enough memory is available to avoid recomputing any integrals on-the-fly, improving performance

This test case is expected to scale efficiently to 1000+ nodes.

\textit{H2O-DFT-LS}

This is a single-point energy calculation for 2048 water molecules in a 39 \AA{}$^{\mathrm{3}}$ box using linear-scaling DFT. A local-density approximation (LDA) functional is used to compute the Exchange-Correlation energy in combination with a DZVP MOLOPT basis set and a 300 Ry cutoff. For large systems, the linear-scaling approach for solving Self-Consistent-Field equations should be much cheaper computationally than using standard DFT, and allow scaling up to 1 million atoms for simple systems. The linear scaling cost results from the fact that the algorithm is based on an iteration on the density matrix. The cubically-scaling orthogonalisation step of standard DFT is avoided and key operations are sparse matrix-matrix multiplications, which have a number of non-zero entries that scale linearly with system size. These are implemented efficiently in CP2K's DBCSR library.

This test case is expected to scale efficiently to 4000+ nodes.

\subsection{3.4 GPAW\label{ref-0064}}

GPAW is a DFT program for ab-initio electronic structure calculations using the projector augmented wave method. It uses a uniform real-space grid representation of the electronic wavefunctions, that allows for excellent computational scalability and systematic converge properties.

\subsubsection{\raisebox{-0pt}{3.4.1} Code description\label{ref-0065}}

GPAW is written mostly in Python, but includes also computational kernels written in C as well as leveraging external libraries such as NumPy, BLAS and ScaLAPACK. Parallelisation is based on message-passing using MPI with no threading. Development branches for GPU and MICs include support for offloading to accelerators using either CUDA or pyMIC, respectively. GPAW is freely available under the GPL license.

\subsubsection{\raisebox{-0pt}{3.4.2} Test cases description\label{ref-0066}}

\textit{Carbon Nanotube}

This test case is a ground state calculation for a carbon nanotube in vacuum. By default, it uses a $6-6-10$ nanotube with 240 atoms (freely adjustable) and serial LAPACK with an option to use ScaLAPACK.

This benchmark is aimed at smaller systems, with an intended scaling range of up to 10 nodes.

\textit{Copper Filament}

This test case is a ground state calculation for a copper filament in vacuum. By default, it uses a 2x2x3 FCC lattice with 71 atoms (freely adjustable) and ScaLAPACK for parallelisation.

This benchmark is aimed at larger systems, with an intended scaling range of up to 100 nodes. A lower limit on the number of nodes may be imposed by the amount of memory required, which can be adjusted to some extent with the run parameters (e.g. lattice size or grid spacing).

\subsection{3.5 GROMACS\label{ref-0067}}

GROMACS is a versatile package to perform molecular dynamics, i.e. simulate the Newtonian equations of motion for systems with hundreds to millions of particles.

It is primarily designed for biochemical molecules like proteins, lipids and nucleic acids that have a lot of complicated bonded interactions, but since GROMACS is extremely fast at calculating the nonbonded interactions (that usually dominate simulations) many groups are also using it for research on non-biological systems, e.g. polymers.

GROMACS supports all the usual algorithms you expect from a modern molecular dynamics implementation, and some additional features:

GROMACS provides extremely high performance compared to all other programs. A lot of algorithmic optimisations have been introduced in the code; for instance, the calculation of the virial has been extracted from the innermost loops over pairwise interactions, and we use our own software routines to calculate the inverse square root. In GROMACS 4.6 and up, on almost all common computing platforms, the innermost loops are written in C using intrinsic functions that the compiler transforms to SIMD machine instructions, to utilise the available instruction-level parallelism. These kernels are available in both single and double precision, and support all different kinds of SIMD support found in x86-family (and other) processors.

\subsubsection{\raisebox{-0pt}{3.5.1} Code description\label{ref-0068}}

Parallelisation is achieved using combined OpenMP and MPI.

Offloading for accelerators is implemented through CUDA for GPU and through OpenMP for MIC (Intel Xeon Phi).

GROMACS is written in C/C++ and freely available under the GPL license.

\subsubsection{\raisebox{-0pt}{3.5.2} Test cases description\label{ref-0069}}

\textit{GluCL Ion Channel}

The ion channel system is the membrane protein GluCl, which is a pentameric chloride channel embedded in a lipid bilayer. The GluCl ion channel was embedded in a DOPC membrane and solvated in TIP3P water. This system contains 142k atoms, and is a quite challenging parallelisation case due to the small size. However, it is likely one of the most wanted target sizes for biomolecular simulations due to the importance of these proteins for pharmaceutical applications. It is particularly challenging due to a highly inhomogeneous and anisotropic environment in the membrane, which poses hard challenges for load balancing with domain decomposition.

This test case was used as the ``Small'' test case in previous 2IP and 3IP PRACE phases. It is included in the package's version 5.0 benchmark cases. It is reported to scale efficiently up to 1000+ cores on x86 based systems.

\textit{Lignocellulose}

A model of cellulose and lignocellulosic biomass in an aqueous solution {\hyperref[ref-0024]{[9]}}. This system of 3.3 million atoms is inhomogeneous. This system uses reaction-field electrostatics instead of PME and therefore scales well on x86. This test case was used as the ``Large'' test case in previous PRACE 2IP and 3IP projects. It is reported in previous PRACE projects to scale efficiently up to 10000+ x86 cores.

\subsection{3.6 NAMD\label{ref-0070}}

NAMD is a widely used molecular dynamics application designed to simulate bio-molecular systems on a wide variety of compute platforms. NAMD is developed by the ``Theoretical and Computational Biophysics Group'' at the University of Illinois at Urbana Champaign. In the design of NAMD particular emphasis has been placed on scalability when utilising a large number of processors. The application can read a wide variety of different file formats, for example force fields, protein structures, which are commonly used in bio-molecular science. A NAMD license can be applied for on the developer's website free of charge. Once the license has been obtained, binaries for a number of platforms and the source can be downloaded from the website. Deployment areas of NAMD include pharmaceutical research by academic and industrial users. NAMD is particularly suitable when the interaction between a number of proteins or between proteins and other chemical substances is of interest. Typical examples are vaccine research and transport processes through cell membrane proteins.

\subsubsection{\raisebox{-0pt}{3.6.1} Code description\label{ref-0071}}

NAMD is written in C++ and parallelised using Charm++ parallel objects, which are implemented on top of MPI, supporting both pure MPI and hybrid parallelisation {\hyperref[ref-0025]{[10]}}.

Offloading for accelerators is implemented for both GPU and MIC (Intel Xeon Phi).

\subsubsection{\raisebox{-0pt}{3.6.2} Test cases description\label{ref-0072}}

The datasets are based on the original "Satellite Tobacco Mosaic Virus (STMV)" dataset from the official NAMD site. The memory optimised build of the package and data sets are used in benchmarking. Data are converted to the appropriate binary format used by the memory optimised build.

\textit{STMV.1M}

This is the original STMV dataset from the official NAMD site. The system contains roughly 1 million atoms. This data set scales efficiently up to 1000+ x86 Ivy Bridge cores.

\textit{STMV.8M}

This is a 2x2x2 replication of the original STMV dataset from the official NAMD site. The system contains roughly 8 million atoms. This data set scales efficiently up to 6000 x86 Ivy Bridge cores.

STMV.28M

This is a 3x3x3 replication of the original STMV dataset from the official NAMD site. The system contains roughly 28 million atoms. This data set also scales efficiently up to 6000 x86 Ivy Bridge cores.

\subsection{3.7 PFARM\label{ref-0073}}

PFARM is part of a suite of programs based on the `R-matrix' ab-initio approach to the varitional solution of the many-electron Schr\"{o}dinger equation for electron-atom and electron-ion scattering. The package has been used to calculate electron collision data for astrophysical applications (such as: the interstellar medium, planetary atmospheres) with, for example, various ions of Fe and Ni and neutral O, plus other applications such as data for plasma modelling and fusion reactor impurities. The code has recently been adapted to form a compatible interface with the UKRmol suite of codes for electron (positron) molecule collisions thus enabling large-scale parallel `outer-region' calculations for molecular systems as well as atomic systems.

\subsubsection{\raisebox{-0pt}{3.7.1} Code description\label{ref-0074}}

In order to enable efficient computation, the external region calculation takes place in two distinct stages, named EXDIG and EXAS, with intermediate files linking the two. EXDIG is dominated by the assembly of sector Hamiltonian matrices and their subsequent eigensolutions. EXAS uses a combined functional/domain decomposition approach where good load-balancing is essential to maintain efficient parallel performance. Each of the main stages in the calculation is written in Fortran 2003 (or Fortran 2003-compliant Fortran 95), is parallelised using MPI and is designed to take advantage of highly optimised, numerical library routines. Hybrid MPI / OpenMP parallelisation has also been introduced into the code via shared memory enabled numerical library kernels.

Accelerator-based implementations have been implemented for both EXDIG and EXAS. EXAS uses offloading via MAGMA (or MKL) for sector Hamiltonian diagonalisations on Intel Xeon Phi and GPU accelerators. EXDIG uses combined MPI and OpenMP to distribute the scattering energy calculations on CPU efficiently both across and within Intel Xeon Phi co-processors.

\subsubsection{\raisebox{-0pt}{3.7.2} Test cases description\label{ref-0075}}

External region R-matrix propagations take place over the outer partition of configuration space, including the region where long-range potentials remain important. The radius of this region is determined from the user input and the program decides upon the best strategy for dividing this space into multiple sub-regions (or sectors). Generally, a choice of larger sector lengths requires the application of larger numbers of basis functions (and therefore larger Hamiltonian matrices) in order to maintain accuracy across the sector and vice-versa. Memory limits on the target hardware may determine the final preferred configuration for each test case.

\textit{Iron, FeIII}

This is an electron-ion scattering case with 1181 channels. Hamiltonian assembly in the coarse region applies 10 Legendre functions leading to Hamiltonian matrix diagonalisations of order 11810. In the `fine energy region' up to 30 Legendre functions may be applied leading to Hamiltonian matrices of up to order 35430. The number of sector calculations is likely to range from about 15 to over 30 depending on the user specifications. Several thousand scattering energies are used in the calculation. 

\textit{Methane, CH4}

The dataset is an electron-molecule calculation with 1361 channels. Hamiltonian dimensions are therefore estimated between 13610 and \textasciitilde{}40000. A process in the code which splits the constituent channels according to spin can be used to approximately halve the Hamiltonian size (whilst doubling the overall number of Hamiltonian matrices). As eigensolvers generally require O(N3) operations, spin splitting leads to a saving in both memory requirements and operation count. The final radius of the external region required is relatively long, leading to more numerous sectors calculations (estimated to between 20 and 30). The calculation will require many thousands of scattering energies.

In the current model, parallelism in EXDIG is limited to the number of sector calculations, i.e a maximum of around 30 accelerator nodes. 

Methane is a relatively new dataset which has not been calculated on novel technology platforms at the very large-scale to date, so this is somewhat a step into the unknown. We are also somewhat reliant on collaborative partners that are not associated with PRACE for continuing to develop and fine tune the accelerator-based EXAS program for this proposed work. Access to suitable hardware with throughput suited to development cycles is also a necessity if suitable progress is to be ensured.

\subsection{3.8 QCD\label{ref-0076}}

Matter consists of atoms, which in turn consist of nuclei and electrons. The nuclei consist of neutrons and protons, which comprise quarks bound together by gluons.

The theory of how quarks and gluons interact to form nucleons and other elementary particles is called Quantum Chromo Dynamics (QCD). For most problems of interest, it is not possible to solve QCD analytically, and instead numerical simulations must be performed. Such ``Lattice QCD'' calculations are very computationally intensive, and occupy a significant percentage of all HPC resources worldwide.

\subsubsection{\raisebox{-0pt}{3.8.1} Code description\label{ref-0077}}

The QCD benchmark benefits of two different implementations described below.

\textit{First implementation}

The MILC code is a freely-available suite for performing Lattice QCD simulations, developed over many years by a collaboration of researchers {\hyperref[ref-0030]{[15]}}.

The benchmark used here is derived from the MILC code (v6), and consists of a full conjugate gradient solution using Wilson fermions. The benchmark is consistent with ``QCD kernel E'' in the full UAEBS, and has been adapted so that it can efficiently use accelerators as well as traditional CPU.

The implementation for accelerators has been achieved using the ``targetDP'' programming model {\hyperref[ref-0031]{[16]}}, a lightweight abstraction layer designed to allow the same application source code to be able to target multiple architectures, e.g. NVIDIA GPU and multicore/manycore CPU, in a performance portable manner. The targetDP syntax maps, at compile time, to either NVIDIA CUDA (for execution on GPU) or OpenMP+vectorisation (for implementation on multi/manycore CPU including Intel Xeon Phi). The base language of the benchmark is C and MPI is used for node-level parallelism.

\textit{Second implementation}

The QCD Accelerator Benchmark suite Part 2 consists of two kernels, the QUDA {\hyperref[ref-0027]{[12]}} and the QPhix {\hyperref[ref-0028]{[13]}} library. The library QUDA is based on CUDA and optimize for running on NVIDIA GPU {\hyperref[ref-0032]{[17]}}. The QPhix library consists of routines which are optimize to use INTEL intrinsic functions of multiple vector length, including optimized routines for KNC and KNL's {\hyperref[ref-0033]{[18]}}. In both QUDA and QPhix, the benchmark kernel uses the conjugate gradient solvers implemented within the libraries.

\subsubsection{\raisebox{-0pt}{3.8.2} Test cases description\label{ref-0078}}

Lattice QCD involves discretisation of space-time into a lattice of points, where the extent of the lattice in each of the 3 spatial and 1 temporal dimensions can be chosen. This means that the benchmark is very flexible, where the size of the lattice can be varied with the size of the computing system in use (weak scaling) or can be fixed (strong scaling). For testing on a single node, then 64x64x32x8 is a reasonable size, since this fits on a single Intel Xeon Phi or a single GPU. For larger numbers of nodes, the lattice extents can be increased accordingly, keeping the geometric shape roughly similar. Test cases for the second implementation are given by a strong-scaling mode with a lattice size of 32x32x32x96 and 64x64x64x128 and a weak scaling mode with a local lattice size of 48x48x48x24.

\subsection{3.9 Quantum Espresso\label{ref-0079}}

QUANTUM ESPRESSO is an integrated suite of computer codes for electronic-structure calculations and materials modelling, based on density-functional theory, plane waves, and pseudopotentials (norm-conserving, ultrasoft, and projector-augmented wave). QUANTUM ESPRESSO stands for \textit{opEn Source Package for Research in Electronic Structure, Simulation, and Optimisation}. It is freely available to researchers around the world under the terms of the GNU General Public License. QUANTUM ESPRESSO builds upon newly restructured electronic-structure codes that have been developed and tested by some of the original authors of novel electronic-structure algorithms and applied in the last twenty years by some of the leading materials modelling groups worldwide. Innovation and efficiency are still its main focus, with special attention paid to massively parallel architectures, and a great effort being devoted to user friendliness. QUANTUM ESPRESSO is evolving towards a distribution of independent and inter-operable codes in the spirit of an open-source project, where researchers active in the field of electronic-structure calculations are encouraged to participate in the project by contributing their own codes or by implementing their own ideas into existing codes.

QUANTUM ESPRESSO is written mostly in Fortran90, and parallelised using MPI and OpenMP and is released under a GPL license.

\subsubsection{\raisebox{-0pt}{3.9.1} Code description\label{ref-0080}}

During 2011 a GPU-enabled version of Quantum ESPRESSO was publicly released. The code is currently developed and maintained by Filippo Spiga at the High Performance Computing Service - University of Cambridge (United Kingdom) and Ivan Girotto at the International Centre for Theoretical Physics (Italy). The initial work has been supported by the EC-funded PRACE and a SFI (Science Foundation Ireland, grant 08/HEC/I1450). At the time of writing, the project is self-sustained thanks to the dedication of the people involved and thanks to NVIDIA support in providing hardware and expertise in GPU programming.

The current public version of QE-GPU is 14.10.0 as it is the last version maintained as plug-in working on all QE 5.x versions. QE-GPU utilised phiGEMM (external) for CPU+GPU GEMM computation, MAGMA (external) to accelerate eigen-solvers and explicit CUDA kernel to accelerate compute-intensive routines. FFT capabilities on GPU are available only for serial computation due to the hard challenges posed in managing accelerators in the parallel distributed 3D-FFT portion of the code where communication is the dominant element that limits excellent scalability beyond hundreds of MPI ranks.

A version for Intel Xeon Phi (MIC) accelerators is not currently available.

\subsubsection{\raisebox{-0pt}{3.9.2} Test cases description\label{ref-0081}}

\textit{PW-IRMOF\_M11}

Full SCF calculation of a Zn-based isoreticular metal--organic framework (total 130 atoms) over 1 K point. Benchmarks run in 2012 demonstrated speedups due to GPU (NVIDIA K20s, with respect to non-accelerated nodes) in the range 1.37 -- 1.87, according to node count (maximum number of accelerators=8). Runs with current hardware technology and an updated version of the code are expected to exhibit higher speedups (probably 2-3x) and scale up to a couple hundred nodes.

\textit{PW-SiGe432}

This is a SCF calculation of a Silicon-Germanium crystal with 430 atoms. Being a fairly large system, parallel scalability up to several hundred, perhaps a 1000 nodes is expected, with accelerated speed-ups likely to be of 2-3x.

\subsection{3.10 Synthetic benchmarks -- SHOC\label{ref-0082}}

The Accelerator Benchmark Suite will also include a series of synthetic benchmarks. For this purpose, we choose the Scalable HeterOgeneous Computing (SHOC) benchmark suite, augmented with a series of benchmark examples developed internally. SHOC is a collection of benchmark programs testing the performance and stability of systems using computing devices with non-traditional architectures for general purpose computing. Its initial focus is on systems containing GPU and multi-core processors, and on the OpenCL programming standard, but CUDA and OpenACC versions were added. Moreover, a subset of the benchmarks is optimised for the Intel Xeon Phi coprocessor. SHOC can be used on clusters as well as individual hosts.

The SHOC benchmark suite currently contains benchmark programs categorised by complexity. Some measure low-level 'feeds and speeds' behaviour (Level 0), some measure the performance of a higher-level operation such as a Fast Fourier Transform (FFT) (Level 1), and the others measure real application kernels (Level 2).

The SHOC benchmark suite has been selected to evaluate the performance of accelerators on synthetic benchmarks, mostly because SHOC provides CUDA/OpenCL/Offload/OpenACC variants of the benchmarks. This allowed us to evaluate NVIDIA GPU (with CUDA/OpenCL/OpenACC), Intel Xeon Phi KNC (with both Offload and OpenCL), but also Intel host CPU (with OpenCL/OpenACC). However, on the latest Xeon Phi processor (codenamed KNL) none of these 4 models is supported. Thus, benchmarks on the KNL architecture can not be run at this point, and there aren't any news of Intel supporting OpenCL on the KNL. However, there is work in progress on the PGI compiler to support the KNL as a target. This support will be added during 2017. This will allow us to compile and run the OpenACC benchmarks for the KNL. Alternatively, the OpenACC benchmarks will be ported to OpenMP and executed on the KNL.

\subsubsection{\raisebox{-0pt}{3.10.1} Code description\label{ref-0083}}

All benchmarks are MPI-enabled. Some will report aggregate metrics over all MPI ranks, others will only perform work for specific ranks.

Offloading for accelerators is implemented through CUDA and OpenCL for GPU and through OpenMP for MIC (Intel Xeon Phi). For selected benchmarks OpenACC implementations are provided for GPU. Multi-node parallelisation is achieved using MPI.

SHOC is written in C++ and is open-source and freely available.

\subsubsection{\raisebox{-0pt}{3.10.2} Test cases description\label{ref-0084}}

The benchmarks contained in SHOC currently feature 4 different sizes for increasingly large systems. The size convention is as follows:

\begin{enumerate}[1]

\item CPU / debugging

\item Mobile/integrated GPU

\item Discrete GPU (e.g. GeForce or Radeon series)

\item HPC-focused or large memory GPU (e.g. Tesla or Firestream Series)

\end{enumerate}

In order to go even larger scale, we plan to add a 5th level for massive supercomputers.

\subsection{3.11 SPECFEM3D\label{ref-0085}}

The software package SPECFEM3D simulates three-dimensional global and regional seismic wave propagation based upon the spectral-element method (SEM). All SPECFEM3D\_GLOBE software is written in Fortran90 with full portability in mind, and conforms strictly to the Fortran95 standard. It uses no obsolete or obsolescent features of Fortran77. The package uses parallel programming based upon the Message Passing Interface (MPI).

The SEM was originally developed in computational fluid dynamics and has been successfully adapted to address problems in seismic wave propagation. It is a continuous Galerkin technique, which can easily be made discontinuous; it is then close to a particular case of the discontinuous Galerkin technique, with optimised efficiency because of its tensorised basis functions. In particular, it can accurately handle very distorted mesh elements. It has very good accuracy and convergence properties. The spectral element approach admits spectral rates of convergence and allows exploiting hp-convergence schemes. It is also very well suited to parallel implementation on very large supercomputers as well as on clusters of GPU accelerating graphics cards. Tensor products inside each element can be optimised to reach very high efficiency, and mesh point and element numbering can be optimised to reduce processor cache misses and improve cache reuse. The SEM can also handle triangular (in 2D) or tetrahedral (3D) elements as well as mixed meshes, although with increased cost and reduced accuracy in these elements, as in the discontinuous Galerkin method.

In many geological models in the context of seismic wave propagation studies (except for instance for fault dynamic rupture studies, in which very high frequencies of supershear rupture need to be modelled near the fault) a continuous formulation is sufficient because material property contrasts are not drastic and thus conforming mesh doubling bricks can efficiently handle mesh size variations. This is particularly true at the scale of the full earth. Effects due to lateral variations in compressional-wave speed, shear-wave speed, density, a 3D crustal model, ellipticity, topography and bathyletry, the oceans, rotation, and self-gravitation are included. The package can accommodate full 21-parameter anisotropy as well as lateral variations in attenuation. Adjoint capabilities and finite-frequency kernel simulations are also included.

\subsubsection{\raisebox{-0pt}{3.11.1} Test cases definition\label{ref-0086}}

Both test cases will use the same input data. A 3D shear-wave speed model (S362ANI) will be used to benchmark the code.

Here is an explanation of the simulation parameters that will be used to size the test case:

\begin{itemize}
\item \textit{NCHUNKS,} number of face of the cubed sphere included in the simulation (will be always 6)

\item \textit{NPROC\_XI}, number of slice along one chunk of the cubed sphere (will represents also the number of processors used for 1 chunk

\item \textit{NEX\_XI}, number of spectral elements along one side of a chunk.

\item \textit{RECORD\_LENGHT\_IN\_MINUTES,} length of the simulated seismograms. The time of the simulation should vary linearly with this parameter.

\end{itemize}
\textit{Small test case} 

It runs with 24 MPI tasks and has the following mesh characteristics: 

\begin{itemize}
\item NCHUCKS=6

\item NPROC\_XI=2

\item NEX\_XI =80 

\item RECORD\_LENGHT\_IN\_MINUTES =2.0

\end{itemize}
\textit{Bigger test case} 

It runs with 150 MPI tasks and has the following mesh characteristics: 

\begin{itemize}
\item NCHUCKS=6

\item NPROC\_XI=5

\item NEX\_XI =80 

\item RECORD\_LENGHT\_IN\_MINUTES =2.0

\end{itemize}
\section{4 Applications performances%Victor CameoVC2017-03-19T19:18:00Z Victor CameoVC Victor CameoVC Victor Cameo Victor Cameo VC VC 2017-03-19T19:18:00Z 2017-03-19T19:18:00Z Faire un tableau r\'{e}cap Faire un tableau r\'{e}cap Faire un tableau r\'{e}cap
\label{ref-0087}\label{ref-0088}}

This section presents some sample results on targeted machines.

\subsection{4.1 Alya\label{ref-0089}}

Alya has been compiled and run using test case A on three different types of compute nodes:

\begin{itemize}
\item BSC MinoTauro Westemere Partition (Intel E5649 12 core 2.53 GHz, 24 GB RAM, Infiniband)

\item BSC MinoTauro Haswell + K80 Partition (Intel Xeon E5-2630 v3 16 core 2.4 GHz, 128 GB RAM, NVIDIA K80, Infiniband)

\item KNL 7250 (68 core 1.40 GHz, 16 GB MCDRAM, 96BG DDR4 RAM, Ethernet)

\end{itemize}
Alya supports parallelism via different options, mainly MPI for problem decomposition, OpenMP within the matrix construction phase and CUDA parallelism for selected solvers. In general, the best distribution and performance can be achieved by using MPI. Running on KNL it has been proven optimal to use 4 OpenMP threads and 16 MPI processes for a total of 64 processes, each on its own physical core. The Xeon Phi processor shows slightly better performance in Alya configured in Quadrant/Cache when compared to Quadrant/Flat, although the difference is negligible. The application is not optimized for the first generation Xeon Phi KNC and does not support offloading.

Overall speedups have been compared to a one node CPU run on the Haswell partition of MinoTauro. As the application is heavily optimized for traditional computation the best and almost linear scaling is observed on the CPU only runs. Some calculations benefit from the accelerators, GPU yielding from 3.6x to 6.5x speedup for one to three nodes. The KNL runs are limited by the OpenMP scalability and too many MPI tasks on these processors lead to suboptimal scaling. Speedups in this case range from 0.9x to 1.6x and can be further optimized by introducing more threading parallelism. The communication overhead when running with many MPI tasks on KNL is noticeable and further limited by the ethernet connection on multinode runs. High-performance fabrics such as Omni-Path or Infiniband promise to provide significant enhancement for these cases. The results are compared in {\hyperref[ref-0092]{Figure 3}}.

It can be seen that the best performance is gained on the most recent standard Xeon CPU in conjunction with GPU. This is expected as Alya has been heavily optimized for traditional HPC scalability using mainly MPI and makes good use of available cores. The addition of GPU enabled solvers provides a noticeable boost to the overall performance. To fully exploit the KNL further optimizations are ongoing and additional OpenMP parallelism will need to be employed.

\begin{figure}
\caption{Figure 1 Shows the matrix construction part of Alya that is parallelised with OpenMP and benefits significantly from the many cores available on KNL.\label{ref-0090}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image3.png}
\label{fig:1}
\end{figure}

\begin{figure}
\caption{Figure 2 Demonstrates the scalability of the code. As expected Haswell cores with K80 GPU are high-performing while the KNL port is currently being optimized further.\label{ref-0091}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image4.png}
\label{fig:2}
\end{figure}

\begin{figure}
\caption{Figure 3 Best performance is achieved with GPU in combination with powerful CPU cores. Single thread performance has a big impact on the speedup, both threading and vectorization are employed for additional performance.\label{ref-0092}\label{ref-0093}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image5.png}
\label{fig:3}
\end{figure}
\subsection{4.2 Code\_Saturne\label{ref-0094}}

\textit{Description runtime architecture:}

\begin{itemize}
\item KNL: ARCHER (model 7210) - The following environment is used, i.e. ENV\_6.0.3. The INTEL compiler's version is 17.0.0.098.

\item GPU: 2 POWER8 nodes, i.e. S822LC (2x P8 10-cores + 2x K80 (2 G210 per K80)) and S824L (2x P8 12-cores + 2x K40 (1 G180 per K40)) - The compiler is at/8.0, the MPI distribution openmpi/1.8.8 and the CUDA compiler's version is 7.5.

\end{itemize}
\textit{3-D Taylor-Green vortex flow (hexahedral cells)}

The first test case has been run on ARCHER KNL and the performance has been investigated for several configurations, each of them using 64 MPI tasks per node and either 1, 2 or 4 hyper-threads (extra MPI tasks) or OpenMP threads have been added for testing. The results are compared to ARCHER CPU, in this case IvyBridge CPU. Up to 8 nodes are used for comparison.

\begin{figure}
\caption{Figure 4 Code\_Saturne's performance on KNL. AMG is used as a solver in V4.2.2.\label{ref-0095}\label{ref-0096}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image6.png}
\label{fig:4}
\end{figure}
{\hyperref[ref-0095]{Figure 4}} shows the CPU time per time step as a function of the number threads/MPI tasks. For all the cases, the time to solution decreases when the number of threads increases. For the case using MPI only and no hyper-threading (green line) only, a simulation is run on half a node as well to investigate the speedup going from half a node to a node, which is about 2 as seen on the figure. The ellipses help comparing the time to solution per node, and finally, a comparison is carried out with simulations run on ARCHER without KNL, using Ivybridge processors. When using 8 nodes, the best configuration for Code\_Saturne to run on KNL is for 64 MPI tasks and 2 OpenMP threads per task (blue line on the figure), which is about 15 to 20\% faster than running on the Ivybridge nodes, using the same number of nodes.

\textit{Flow in a 3-D lid-driven cavity (tetrahedral cells)}

The following options are used for PETSc: -

\begin{itemize}
\item -CPU: -ksp\_type = cg and -pc\_type = jacobi

\item -GPU: -ksp\_type = cg and -vec\_type = cusp and -mat\_type = aijcusp and -pc\_type = jacobi

\end{itemize}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image7.emf}

\textbf{Table 3 Performance of Code\_Saturne + PETSc on 1 node of the POWER8 clusters. Comparison between 2 different nodes, using different types of CPU and GPU. PETSc is built on LAPACK. The speedup is computed at the ratio between the time to solution on the CPU for a given number of MPI tasks and the time to solution on the CPU/GPU for the same number of MPI tasks.\label{ref-0097}\label{ref-0098}}

\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image8.emf}

\textbf{Table 4 Performance of Code\_Saturne and PETSc on 1 node of KNL. PETSc is built on the MKL library\label{ref-0099}\label{ref-0100}}

{\hyperref[ref-0097]{Table 3}} and {\hyperref[ref-0099]{Table 4}} show the results obtained using POWER8 CPU and CPU/GPU, and KNL, respectively. Focusing on the results on the POWER8 nodes first, a speedup is observed on each node of the POWER8, when using the same number of MPI tasks and of GPU. However, when the nodes are fully populated (20 and 24 MPI tasks, respectively), it is cheaper to run on the CPU only than using CPU/GPU. This could be explained by the fact that the same overall amount of data is transferred but the system administration costs, latency costs, asynchronicity of transfer in 20 (S822LC) or 24 (S824L) slices might be prohibitive.

\subsection{4.3 CP2K\label{ref-0101}}

Times shown in the ARCHER KNL (model 7210, 1.30GHz, 96GB memory DDR) vs Ivy Bridge (E5-2697 v2, 2.7 GHz, 64GB) plot are for those CP2K threading configurations that give the best performance in each case. The shorthand for naming threading configurations is:

\begin{itemize}
\item MPI: pure MPI

\item X\_TH: X OpenMP threads per MPI rank

\end{itemize}
Whilst single-threaded pure MPI or 2 OpenMP threads is often fastest on conventional processors, on the KNL multithreading is more likely to be beneficial, especially in problems such as the LiH-HFX benchmark in which having fewer MPI ranks means more memory is available to each rank, allowing partial results to be stored in memory instead of expensively recomputed on the fly. 

Hyperthreads were left disabled (equivalent to the aprun option --j 1), as no significant performance benefit was observed using hyperthreading.

\begin{figure}
\caption{Figure 5 Test case 1 of CP2K on the ARCHER cluster\label{ref-0102}\label{ref-0103}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image9.png}
\label{fig:5}
\end{figure}
The node based comparison shows ({\hyperref[ref-0102]{Figure 5}}) that the runtimes on KNL nodes are roughly 1.7 times slower than runtimes on 2-socket IvyBridge nodes.

\subsection{4.4 GPAW\label{ref-0104}}

The performance of GPAW using both benchmarks was measured with a range of parallel job sizes on several architectures; with the architectures designated in the following tables, figures, and text as:

\begin{itemize}
\item CPU: x86 Haswell CPU (Intel Xeon E5-2690v3) in a dual-socket node

\item KNC: Knights Corner MIC (Intel Xeon Phi 7120P) with a x86 Haswell host CPU (Intel Xeon E5-2680v3) in a dual-socket node

\item KNL: Knights Landing MIC (Intel Xeon Phi 7210) in a single-socket node

\item K40: K40 GPU (NVIDIA Tesla K40) with a x86 Ivy Bridge host CPU (Intel Xeon E5-2620-v2) in a dual-socket node

\item K80: K80 GPU (NVIDIA Tesla K80) with a x86 Haswell host CPU (Intel Xeon E5-2680v3) in a quad-socket node

\end{itemize}
Only time spent in the main SCF-cycle was used as the runtime in the comparison ({\hyperref[ref-0105]{Table 5}} and {\hyperref[ref-0107]{Table 6}}) to exclude any differences in the initialisation overheads.

\includegraphics[width=0.5\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image10.emf}\includegraphics[width=0.5\textwidth]{embeddings/Microsoft_Excel_Worksheet2.xlsx}

\textbf{Table 5 GPAW runtimes (in seconds) for the smaller benchmark (Carbon Nanotube) measured on several architectures when using n sockets (i.e. processors or accelerators).\label{ref-0105}\label{ref-0106}}

\includegraphics[width=0.5\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image11.emf}\includegraphics[width=0.5\textwidth]{embeddings/Microsoft_Excel_Worksheet3.xlsx}

\textbf{Table 6 GPAW runtimes (in seconds) for the larger benchmark (Copper Filament) measured on several architectures when using n sockets (i.e. processors or accelerators). *Due to memory limitations on the GPU the grid spacing was increased from 0.22 to 0.28 to have a sparser grid. To account for this in the comparison, the K40 and K80 runtimes have been scaled up using a corresponding CPU runtime as a yardstick (scaling factor q=2.1132).\label{ref-0107}\label{ref-0108}}

As can been seen from Table 2 and Table 3, in both benchmarks a single KNL or K40/K80 was faster than a single CPU. But when using multiple KNL, the performance does not seem to scale as well as for CPU. In the smaller benchmark (Carbon Nanotube), CPU outperform KNL when using more than 2 processors. In the larger benchmark (Copper Filament), KNL still outperform CPU with 8 processors but it seems likely that the CPU will overtake KNL when using an even larger number of processors.

In contrast to KNL, the older KNC are slower than Haswell CPU across the board. Nevertheless, as can been seen from Figure 4, the scaling of KNC is to some extend comparable to CPU but with a lower scaling limit. It is therefore likely that, on systems with considerably slower host CPU than Haswells (e.g. Ivy Bridges), KNC may also give a performance boost over the host CPU.

\begin{figure}
\caption{Figure 6 Relative performance (to / t) of GPAW is shown for parallel jobs using an increasing number of CPU (blue) or Xeon Phi KNC (red). Single CPU SCF-cycle runtime (to) was used as the baseline for the normalisation. Ideal scaling is shown as a linear dashed line for comparison. Case 1 (Carbon Nanotube) is shown with square markers and Case 2 (Copper Filament) is shown with round markers. \label{ref-0109}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image12.png}
\label{fig:6}
\end{figure}
\subsection{4.5 GROMACS\label{ref-0110}}

Gromacs was successfully compiled and ran on the following systems:

\begin{itemize}
\item GRNET ARIS: Thin nodes (E5-2680v2), GPU nodes (Dual E5-2660v3+ Dual K40m), all with FDR14 Infiniband, Single node KNL 7210. 

\item CINES Frioul KNL 7230

\item IDRIS Ouessant: IBM Power 8 + Dual P100

\end{itemize}
On KNL machines the runs were performed using Quadrant processor and both Cache / Flat memory configuration. On GRNET's single node KNL more configurations were tested. 

As it is expected the Quandrant/Cache mode gives the best performance for all cases. The performance dependence on the MPI Tasks/OpenMP threads combination was also explored. In most cases 66 tasks/per node using 2 or 4 threads/task gives the best performance on KNL 7230.

In all accelerated runs a speed up of 2-2.6x with respect CPU only was achieved with GPU. Gromacs does not support offload on KNC.

\begin{figure}
\caption{Figure 7 Scalability for GROMACS test case GluCL Ion Channel\label{ref-0111}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image13.png}
\label{fig:7}
\end{figure}

\begin{figure}
\caption{Figure 8 Scalability for GROMACS test case Lignocellulose\label{ref-0112}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image14.png}
\label{fig:8}
\end{figure}
\subsection{4.6 NAMD\label{ref-0113}}

NAMD was successfully compiled and ran on the following systems:

\begin{itemize}
\item GRNET ARIS : Thin nodes (E5-2680v2), GPU nodes (Dual E5-2660v3+ Dual K40m), KNC Nodes (Dual E5-2660v2+Dual KNC 7120P), all with FDR14 Infiniband, Single node KNL 7210.

\item Cines Frioul : KNL 7230 

\item Cines Ouessant : IBM Power 8 + Dual P100

\end{itemize}
On KNL machines the runs were performed using Quadrant processor and both Cache / Flat memory configuration. On GRNET's single node KNL more configurations were tested. 

As it is expected the Quandrant/Cache mode gives the best performance for all cases. The performance dependence on the MPI Tasks/OpenMP threads combination was also explored. 

In most cases 66 tasks per node using 4 threads/task or 4 tasks per node/64 threads per task gives the best performance on KNL 7230.

In all accelerated runs a speed up of 5-6x with respect CPU only runs was achieved with GPU.

On KNC the speed up with respect CPU only is in the range 2-3.5 in all cases.

\begin{figure}
\caption{Figure 9 Scalability for NAMD test case STMV.8M\label{ref-0114}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image15.png}
\label{fig:9}
\end{figure}

\begin{figure}
\caption{Figure 10 Scalability for NAMD test case STMV.28M\label{ref-0115}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image16.png}
\label{fig:10}
\end{figure}
\subsection{4.7 PFARM\label{ref-0116}}

The code has been tested and timed on several architectures, designated in the following figures, tables and text as:

\begin{itemize}
\item CPU: node contains two 2.7 GHz, 12-core E5-2697 v2 (Ivy Bridge) series processors with 64GB memory.

\item KNL: node is a 64-core KNL processor (model 7210) running at 1.30GHz with 96GB of memory.

\item GPU: node contains a dual socket 16-core Haswell E5-2698 running at 2.3 GHz with 256GB memory and 4 K40, 4 K80 or 4 P100 GPU.

\end{itemize}
Codes on all architectures are compiled with the Intel compiler (CPU v15, KNL \& GPU v17).

The divide-and-conquer eigensolver routine DSYEVD is used throughout the test runs. The routine is linked from the following numerical libraries:

\begin{itemize}
\item CPU: Intel MKL Version 11.2.2

\item KNL: Intel MKL Version 2017 Initial Release

\item GPU: MAGMA Version 2.2

\end{itemize}

\begin{figure}
\caption{Figure 11 Eigensolver performance on KNL and GPU\label{ref-0117}\label{ref-0118}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image17.png}
\label{fig:11}
\end{figure}
EXDIG calculations are dominated by the eigensolver operations required to diagonalize each sector Hamiltonian matrix. {\hyperref[ref-0117]{Figure 11}} summarizes eigensolver performance, using DSYEVD, over a range of problem sizes for the Xeon (CPU), Intel Knight's Landing (KNL) and a range of recent Nvidia GPU architectures. The results are normalised to the single node CPU performance using 24 OpenMP threads. The CPU runs use 24 OpenMP threads and the KNL runs use 64 OpenMP threads. Dense linear algebra calculations tend to be bound by memory bandwidth, so using hyperthreading on the KNL or CPU is not beneficial. MAGMA is able to parallelise the calculation automatically across multiple GPU on a compute node and these results are denoted by the x2, x4 labels. {\hyperref[ref-0117]{Figure 11}} demonstrates that MAGMA performance relative to CPU performance increases as problem size increases, due to the relative overhead cost of data transfer O(N\textasciicircum{}2) reducing compared to computational load O(N\textasciicircum{}3).

\textit{Test Case 1 -- FeIII}

Defining Computational Characteristics: 10 Fine Region Sector calculations involving Hamiltonian matrices of dimension 23620 and 10 Coarse Region Sector calculations involving Hamiltonian matrices of dimension 11810.

\textit{Test Case 2 -- CH4}

Defining Computational Characteristics: 10 `Spin 1' Coarse Sector calculations involving Hamiltonian matrices of dimension 5720 and 10 `Spin 2' Coarse Sector calculations involving Hamiltonian matrices of dimension 7890.

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.19\linewidth-2\tabcolsep}
p{\dimexpr 0.13\linewidth-2\tabcolsep}
p{\dimexpr 0.12\linewidth-2\tabcolsep}
p{\dimexpr 0.08\linewidth-2\tabcolsep}
p{\dimexpr 0.09\linewidth-2\tabcolsep}
p{\dimexpr 0.09\linewidth-2\tabcolsep}
p{\dimexpr 0.08\linewidth-2\tabcolsep}
p{\dimexpr 0.1\linewidth-2\tabcolsep}
p{\dimexpr 0.1\linewidth-2\tabcolsep}}
 & CPU 24 threads & KNL 64 threads & K80 & K80x2 & K80x4 & P100 & P100x2 & P100x4 \\
Test Case 1~; Atomic~; FeIII & 4475 & 2610 & 1215 & 828 & 631 & 544 & 427 & 377 \\
Test Case 2~; Molecular~; CH4 & 466 & 346 & 180 & 150 & 134 & 119 & 107 & 111 \\

\end{tabularx}

\end{table}

\textbf{Table 7 Overall EXDIG runtime performance on various accelerators (runtime, secs)\label{ref-0119}\label{ref-0120}}

{\hyperref[ref-0119]{Table 7}} records the overall run time on a range of architectures for both test cases described. For the complete runs (including I/O), both KNL-based and GPU-based computations significantly outperform the CPU-based calculations. For Test Case 1, utilising a node with single P100 GPU accelerator results in a runtime more than 8 times quicker than the CPU, correspondingly approximately 4 times quicker for Test Case 2. The smaller Hamiltonian matrices associated with Test Case 2 means that data transfer costs O(N2) are relatively high vs computation costs O(N3). Smaller matrices also result in poorer scaling as we increase the number of GPU per node for Test Case 2.

\textbf{\includegraphics[width=0.5\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image18.emf}\includegraphics[width=0.5\textwidth]{embeddings/Microsoft_Excel_Worksheet4.xlsx}}

\textbf{Table 8 Overall EXDIG runtime parallel performance using MPI-GPU version\label{ref-0121}\label{ref-0122}}

A relatively simple MPI harness can be used in EXDIG to farm out different sector Hamiltonian calculations to multiple CPU, KNL or GPU nodes. {\hyperref[ref-0121]{Table 8}} shows that parallel scaling across nodes is very good for each test platform. This strategy is inherently scalable, however the replicated data approach requires significant amounts of memory per node. Test Case 1 is used as the dataset here, although the problem characteristics are slightly different to the setup used for {\hyperref[ref-0119]{Table 7}}, with 5 Fine Region sectors with Hamiltonian dimension of 23620 and 20 Coarse Region sectors with Hamiltonian dimension of 11810. With these characteristics, runs using 2 MPI tasks experience inferior load-balancing in the Fine Region calculation compared to runs using 5 MPI tasks.

\subsection{4.8 QCD\label{ref-0123}}

As stated in the description, QCD benchmark has two implementations.

\subsubsection{\raisebox{-0pt}{4.8.1} First implementation\label{ref-0124}}

\begin{figure}
\caption{Figure 12 Small test case results for QCD, first implementation\label{ref-0125}\label{ref-0126}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image19.png}
\label{fig:12}
\end{figure}

\begin{figure}
\caption{Figure 13 Large test case results for QCD, first implementation\label{ref-0127}\label{ref-0128}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image20.png}
\label{fig:13}
\end{figure}
The strong scaling, on Titan and ARCHER, for small ({\hyperref[ref-0125]{Figure 12}}) and large ({\hyperref[ref-0127]{Figure 13}}) problem sizes. For ARCHER, both CPU are used per node. For Titan, we include results with and without GPU utilization.

On each node, Titan has one 16-core Interlagos CPU and one K20X GPU, whereas ARCHER has two 12-core Ivy-bridge CPU. In this section, we evaluate on a node-by-node basis. For Titan, a single MPI task per node, operating on the CPU, is used to drive the GPU on that node. We also include, for Titan, results just using the CPU on each node without any involvement from the GPU, for comparison. This means that, on a single node, our Titan results will be the same as those K20X and Interlagos results presented in the previous section (for the same test case). On ARCHER, however, we fully utilize both the processors per node: to do this we use two MPI tasks per node, each with 12 OpenMP threads (via targetDP). So the single node results for ARCHER are twice as fast as those Ivy-bridge single-processor results presented in the previous section.

\begin{figure}
\caption{Figure 14 shows the time taken by the full MILC 64x64x64x8 test cases on traditional CPU, Intel Knights Landing Xeon Phi and NVIDIA P100 (Pascal) GPU architectures.\label{ref-0129}\label{ref-0130}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image21.emf}
\label{fig:14}
\end{figure}
In {\hyperref[ref-0129]{Figure 14}} we present preliminary results for on the latest generation Intel Knights Landing (KNL) and NVIDIA Pascal architectures, which offer very high bandwidth stacked memory, together with the same traditional Intel-Ivy-bridge CPU used in previous sections. Note that these results are not directly comparable with those presented earlier, since they are for a different test case size (larger since we are no longer limited by the small memory size of the Knights Corner), and they are for a slightly updated verion of the benchmark. The KNL is the 64-core 7210 model, available from within a test and development platform provided as part of the ARCHER service. The Pascal is a NVIDIA P100 GPU provided as part of the ``Ouessant'' IBM service at IDRIS, where the host CPU is an IBM Power8+.

It can be seen that the KNL is 7.5X faster than the Ivy-bridge; the Pascal is 13X faster than the Ivy-bridge; and the Pascal is 1.7X faster than the KNL. 

\subsubsection{\raisebox{-0pt}{4.8.2} Second implementation\label{ref-0131}}

\textit{GPU results}

The GPU benchmark results of the second implementation are done on PizDaint located in Switzerland at CSCS and the GPU-partition of Cartesius at Surfsara based in Netherland, Amsterdam. The runs are performed by using the provided bash-scripts. PizDaint is equipped with one P100 Pascal-GPU per node. Two different test-cases are depicted, the "strong-scaling" mode with a random lattice configuration of size 32x32x32x96 and 64x64x64x128. The GPU nodes of Cartesius have two Kepler-GPU K40m per node and the "strong-scaling" test is shown for one card per node and for two cards per node. The benchmark kernel is using the conjugated gradient solver which solve a linear equation system given by D * x = b, for the unknown solution "x" based on the clover improved Wilson Dirac operator "D" and a known right hand side "b".

\begin{figure}
\caption{Figure 15 Result of second implementation of QCD on K40m GPU\label{ref-0132}\label{ref-0133}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image22.png}
\label{fig:15}
\end{figure}
{\hyperref[ref-0132]{Figure 15}} shows strong scaling of the conjugate gradient solver on K40m GPU on Cartesius. The lattice size is given by 32x32x32x96, which corresponds to a moderate lattice size nowadays. The test is performed with a mixed precision CG in double-double mode (red) and half-double mode (blue). The run is done on one GPU per node (filled) and two GPU nodes per node (non-filled).

\begin{figure}
\caption{Figure 16 Result of second implementation of QCD on P100 GPU\label{ref-0134}\label{ref-0135}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image23.png}
\label{fig:16}
\end{figure}
{\hyperref[ref-0134]{Figure 16}} shows strong scaling of the conjugate gradient solver on P100 GPU on PizDaint. The lattice size is given by 32x32x32x96 similar to the strong scaling run on the K40m on Cartesius. The test is performed with mixed precision CG in double-double mode (red) and half-double mode (blue).

\begin{figure}
\caption{Figure 17 Result of second implementation of QCD on P100 GPU on larger test case\label{ref-0136}\label{ref-0137}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image24.png}
\label{fig:17}
\end{figure}
{\hyperref[ref-0136]{Figure 17}} shows strong scaling of the conjugate gradient solver on P100 GPU on PizDaint. The lattice size is increase to 64x64x64x128, which is a large lattice nowadays. By increasing the lattice the scaling test shows that the conjugate gradient solver has a very good strong scaling up to 64 GPU.

\textit{Xeon Phi results}

The benchmark results for the XeonPhi benchmark suite are performed on Frioul at CINES, and the hybrid partition on MareNostrum III at BSC. Frioul has one KNL-card per node while the hybrid partition of MareNostrum III is equipped with two KNC per node. The data on Frioul are generated by using the bash-scripts provided by the second implementation of QCD and are done for the two test cases "strong-scaling" with a lattice size of 32x32x32x96 and 64x64x64x128. In case of the data generated at MareNostrum, data for the "strong-scaling" mode on a 32x32x32x96 lattice are shown. The benchmark kernel uses a random gauge configuration and the conjugated gradient solver to solve a linear equation involving the clover Wilson Dirac operator.

\begin{figure}
\caption{Figure 18 Result of second implementation of QCD on KNC\label{ref-0138}\label{ref-0139}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image25.png}
\label{fig:18}
\end{figure}
{\hyperref[ref-0138]{Figure 18}} shows strong scaling of the conjugate gradient solver on KNC's on the hybrid partition on MareNostrum III. The lattice size is given by 32x32x32x96, which corresponds to a moderate lattice size nowadays. The test is performed with a conjugate gradient solver in single precision by using the native mode and 60 OpenMP tasks per MPI process. The run is done on one KNC per node (filled) and two KNC node per node (non-filled).

\begin{figure}
\caption{Figure 19 Result of second implementation of QCD on KNL\label{ref-0140}\label{ref-0141}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image26.png}
\label{fig:19}
\end{figure}
{\hyperref[ref-0140]{Figure 19}} shows strong scaling results of the conjugate gradient solver on KNL's on Frioul. The lattice size is given by 32x32x32x96 which is similar to the strong scaling run on the KNC on MareNostrum III. The run is performed in quadrantic cache mode with 68 OpenMP processes per KNL. The test is performed with a conjugate gradient solver in single precision.

\subsection{4.9 Quantum Espresso\label{ref-0142}}

Here are sample results for Quantum Espresso. This code has run on Cartesius (see section {\hyperref[ref-0046]{2.2.1}}) and Marconi (1 node is 1 standalone KNL Xeon Phi 7250, 68 core 1.40 GHz, 16BG MCDRAM, 96BG DDR4 RAM, interconnect is Intel OmniPath).

\textit{Runs on GPU}

\begin{figure}
\caption{Figure 20 Scalability of Quantum Espresso on GPU for test case 1\label{ref-0143}\label{ref-0144}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image27.png}
\label{fig:20}
\end{figure}

\begin{figure}
\caption{Figure 21 Scalability of Quantum Espresso on GPU for test case 2\label{ref-0145}\label{ref-0146}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image28.png}
\label{fig:21}
\end{figure}
Test cases ({\hyperref[ref-0143]{Figure 20}} and {\hyperref[ref-0145]{Figure 21}}) show no appreciable speed-up with GPU. Inputs are probably too small, they should evolve in the future of this benchmark suite.

\textit{Runs on KNL}

\begin{figure}
\caption{Figure 22 Scalability of Quantum Espresso on KNL for test case 1\label{ref-0147}\label{ref-0148}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image29.png}
\label{fig:22}
\end{figure}
{\hyperref[ref-0147]{Figure 22}} shows the usual pw.x with the small test case A (AUSURF), comparing Marconi Broadwell (36 cores/node) with KNL (68 cores/node) - this test case is probably small for testing on KNL.

\begin{figure}
\caption{Figure 23 Quantum Espresso - KNL vs BDW vs BGQ (at scale)\label{ref-0149}\label{ref-0150}}
\includegraphics[width=1\textwidth]{d7.5_4IP_1.0.docx.tmp/word/media/image30.png}
\label{fig:23}
\end{figure}
{\hyperref[ref-0149]{Figure 23}} presents CNT10POR8 which is the large test case, even though it is using the cp.x executable (i.e. Car-parinello) rather than the usual pw.x (PW SCF calculation).

\subsection{4.10 Synthetic benchmarks (SHOC)\label{ref-0151}\label{ref-0152}}

The SHOC benchmark has been run on Cartesius, Ouessant and MareNostrum. {\hyperref[ref-0153]{Table 9}} presents the results:

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.25\linewidth-2\tabcolsep}
p{\dimexpr 0.13\linewidth-2\tabcolsep}
p{\dimexpr 0.13\linewidth-2\tabcolsep}
p{\dimexpr 0.13\linewidth-2\tabcolsep}
p{\dimexpr 0.1\linewidth-2\tabcolsep}
p{\dimexpr 0.12\linewidth-2\tabcolsep}
p{\dimexpr 0.13\linewidth-2\tabcolsep}}
 & \multicolumn{3}{l}{NVIDIA GPU} & \multicolumn{3}{l}{Intel Xeon Phi} \\
 & K40 CUDA & K40 OpenCL & Power 8 + P100 CUDA & KNC Offload & KNC OpenCL & Haswell OpenCL \\
BusSpeedDownload & 10.5 GB/s & 10.56 GB/s & 32.23 GB/s & 6.6 GB/s & 6.8 GB/s & 12.4 GB/s \\
BusSpeedReadback & 10.5 GB/s & 10.56 GB/s & 34.00 GB/s & 6.7 GB/s & 6.8 GB/s & 12.5 GB/s \\
maxspflops & 3716 GFLOPS & 3658 GFLOPS & 10424 GFLOPS & \textcolor{color-4}{21581} & \textcolor{color-4}{2314 GFLOPS} & 1647 GFLOPS \\
maxdpflops & 1412 GFLOPS & 1411 GFLOPS & 5315 GFLOPS & \textcolor{color-4}{16017} & \textcolor{color-4}{2318 GFLOPS} & 884 GFLOPS \\
gmem\_readbw & 177 GB/s & 179 GB/s & 575.16 GB/s & 170 GB/s & 49.7 GB/s & 20.2 GB/s \\
gmem\_readbw\_strided & 18 GB/s & 20 GB/s & 99.15 GB/s & N/A & 35 GB/s & \textcolor{color-4}{156 GB/s} \\
gmem\_writebw & 175 GB/s & 188 GB/s & 436 GB/s & 72 GB/s & 41 GB/s & 13.6 GB/s \\
gmem\_writebw\_strided & 7 GB/s & 7 GB/s & 26.3 GB/s & N/A & 25 GB/s & \textcolor{color-4}{163 GB/s} \\
lmem\_readbw & 1168 GB/s & 1156 GB/s & 4239 GB/s & N/A & 442 GB/s & 238 GB/s \\
lmem\_writebw & 1194 GB/s & 1162 GB/s & 5488 GB/s & N/A & 477 GB/s & 295 GB/s \\
BFS & 49,236,500 Edges/s & 42,088,000 Edges/s & 91,935,100 Edges/s & N/A & 1,635,330 Edges/s & 14,225,600 Edges/s \\
FFT\_sp & 523 GFLOPS & 377 GFLOPS & 1472 GFLOPS & 135 GFLOPS & 71 GFLOPS & 80 GFLOPS \\
FFT\_dp & 262 GFLOPS & 61 GFLOPS & 733 GFLOPS & 69.5 GFLOPS & 31 GFLOPS & 55 GFLOPS \\
SGEMM & 2900-2990 GFLOPS & 694/761 GFLOPS & 8604-8720 GFLOPS & 640/645 GFLOPS & 179/217 GFLOPS & 419-554 GFLOPS \\
DGEMM & 1025-1083 GFLOPS & 411/433 GFLOPS & 3635-3785 GFLOPS & 179/190 GFLOPS & 76/100 GFLOPS & 189-196 GFLOPS \\
MD (SP) & 185 GFLOPS & 91 GFLOPS & 483 GFLOPS & 28 GFLOPS & 33 GFLOPS & 114 GFLOPS \\
MD5Hash & 3.38 GH/s & 3.36 GH/s & 15.77 GH/s & N/A & 1.7 GH/s & 1.29 GH/s \\
Reduction & 137 GB/s & 150 GB/s & 271 GB/s & 99 GB/s & 10 GB/s & 91 GB/s \\
Scan & 47 GB/s & 39 GB/s & 99.2 GB/s & 11 GB/s & 4.5 GB/s & 15 GB/s \\
Sort & 3.08 GB/s & 0.54 GB/s & 12.54 GB/s & N/A & 0.11 GB/s & 0.35 GB/s \\
Spmv & 4-23 GFLOPS & 3-17 GFLOPS & 23-65 GFLOPS & \textcolor{color-4}{1-17944 GFLOPS} & N/A & 1-10 GFLOPS \\
Stencil2D & 123 GFLOPS & 135 GFLOPS & 465 GFLOPS & 89 GFLOPS & 8.95 GFLOPS & 34 GFLOPS \\
Stencil2D\_dp & 57 GFLOPS & 67 GFLOPS & 258 GFLOPS & 16 GFLOPS & 7.92 GFLOPS & 30 GFLOPS \\
Triad & 13.5 GB/s & 9.9 GB/s & 43 GB/s & 5.76 GB/s & 5.57 GB/s & 8 GB/s \\
S3D (level2) & 94 GFLOPS & 91 GFLOPS & 294 GFLOPS & 109 GFLOPS & 18 GFLOPS & 27 GFLOPS \\

\end{tabularx}

\end{table}

\textbf{Table 9 Synthetic benchmarks results on GPU and Xeon Phi\label{ref-0153}\label{ref-0154}}

Measures marked red are not relevant and should not be considered:

\begin{itemize}
\item KNC MaxFlops (both SP and DP): In this case the compiler optimizes away some of the computation (although it shouldn't) {\hyperref[ref-0034]{[19]}}.

\item KNC SpMV: For these benchmarks it is a known bug currently being addressed {\hyperref[ref-0035]{[20]}}.

\item Haswell gmem\_readbw\_strided and gmem\_writebw\_strided: strided read/write benchmarks doesn't make too much sense in the case of the CPU, as the data will be cache in the large L3 caches. It is reason why we see high number only in the Haswell case.

\end{itemize}
\subsection{4.11 SPECFEM3D\label{ref-0155}}

Tests have been carried out on Ouessant and Firoul.

So far it has only been possible to run on one fixed core count for each test case, so scaling curves are not available. Test case A ran on 4 KNL and 4 P100. Test case B ran on 10 KNL and 4 P100.

\begin{table}
\begin{tabularx}{\textwidth}{
p{\dimexpr 0.4\linewidth-2\tabcolsep}
p{\dimexpr 0.27\linewidth-2\tabcolsep}
p{\dimexpr 0.33\linewidth-2\tabcolsep}}
 & KNL & P100 \\
Test case A & 66 & 105 \\
Test case B & 21.4 & 68 \\

\end{tabularx}

\end{table}

\textbf{Table 10 SPECFEM 3D GLOBE results (run time in second)\label{ref-0156}}

\section{5 Conclusion and future work\label{ref-0157}\label{ref-0158}}

The work presented here stand as a first sight for application benchmarking on accelerators. Most codes have been selected among the main Unified European Application Benchmark Suite. This paper describes each of them as well as implementation, relevance to European science community and test cases. We have presented results on leading edge systems

The suite will be publicly available on the PRACE web site {\hyperref[ref-0016]{[1]}} where links to download sources and test cases will be published along with compilation and run instructions.

Task 7.2B in PRACE 4IP started to design a benchmark suite for accelerators. This work has been done aiming at integrating it to the main UEABS one so that both can be maintained and evolve together. As PCP (PRACE-3IP) machines will soon be available, it will be very interesting to run the benchmark suite on them. First because these machines will be larger, but also because they will feature energy consumption probes.

\end{document}
