Computational Hydrodynamics: How Portable and Scalable Are Heterogeneous Programming Paradigms?

Wojciech Pawlak, Stefan Lemvig Glimberg, Allan Peter Engsig-Karup

Research output: Contribution to conferencePosterResearchpeer-review

162 Downloads (Pure)

Abstract

New many-core era applications at the interface of mathematics and computer science adopt modern parallel programming paradigms and expose parallelism through proper algorithms. We present new performance results for a novel massively parallel free surface wave model suitable for advanced simulations in arbitrary size Numerical Wave Tanks.
The application has already been studied in a series of works (see References) and is demonstrated to exhibit excellent performance portability and scalability using hybrid MPI-OpenCL/CUDA. Furthermore, it can be executed on arbitrary heterogeneous multi-device system sizes from desktops to large HPC systems such as superclusters and in the cloud utilizing heterogeneous devices like multi-core CPUs, GPUs, and Xeon Phi coprocessors.
The numerical efficiency is evaluated on heterogeneous devices like multi-core CPUs, GPUs and Xeon Phi coprocessors to test the performance with respect to both portability and scalability.
This study contributes to investigating the potential of code acceleration for reducing turn-around times of industrial CFD applications on heterogeneous hardware.
Original languageEnglish
Publication date2015
Number of pages1
Publication statusPublished - 2015
EventSIAM Conference on Computational Science and Engineering (SIAM CSE 2015) - Salt Lake City, Utah, United States
Duration: 4 Mar 201518 Mar 2015
https://www.siam.org/meetings/cse15/

Conference

ConferenceSIAM Conference on Computational Science and Engineering (SIAM CSE 2015)
Country/TerritoryUnited States
CitySalt Lake City, Utah
Period04/03/201518/03/2015
Internet address

Fingerprint

Dive into the research topics of 'Computational Hydrodynamics: How Portable and Scalable Are Heterogeneous Programming Paradigms?'. Together they form a unique fingerprint.

Cite this