Leveraging MPI RMA to optimize halo‐swapping communications in MONC on Cray machines. (25th September 2018)

• Record Type: Journal Article
• Authors: Brown, Nick; Bareford, Michael; Weiland, Michèle
• Other Names: Thota Abhinav guestEditor.; He Yun guestEditor.; Hart David guestEditor.; Dahan Maytal guestEditor.; Navratil Paul guestEditor.
• Is Part Of: Concurrency and computation. Volume 31:Number 16(2019)
• Page Start: n/a
• Page End: n/a
• Publication Date: 2018-09-25
• Subjects: ARCHER -- cirrus -- Cray XC30 -- MONC -- MPI RMA -- one sided communications -- SGI ICE; Parallel processing (Electronic computers) -- Periodicals; Parallel computers -- Periodicals; 004.35
• DOI: 10.1002/cpe.5008
• Languages: English
• ISSNs: 1532-0626

Abstract

Summary: Remote Memory Access (RMA), also known as single‐sided communications, provides a way for reading and writing directly into the memory of other processes without having to issue explicit message passing style communication calls. Previous studies have concluded that MPI RMA can provide increased communication performance over traditional MPI Point to Point (P2P), but these are based on synthetic benchmarks rather than real‐world codes. In this work, we replace the existing non‐blocking P2P communication calls in the Met Office NERC Cloud model, a mature code for modeling the atmosphere, with MPI RMA. We describe our approach in detail and discuss the options taken for correctness and performance. Experiments are performed on ARCHER, a Cray XC30, and Cirrus, an SGI ICE machine. We demonstrate on ARCHER that, by using RMA, we can obtain between a 5% and 10% reduction in communication time at each timestep on up to 32768 cores, which over the entirety of a run (with many timesteps) results in a significant improvement in performance compared to P2P on the Cray. However, RMA is not a silver bullet, and there are challenges when integrating RMA calls into existing codes: important optimizations are necessary to achieve good performance and library support is not universally mature, as is the case on Cirrus. In this paper, we discuss, in the context of a real‐world code, the lessons learned converting P2P to RMA, explore performance and scaling challenges, and contrast alternative RMA synchronization approaches in detail.