Track papers across labs, topics, and trends.
Search papers, labs, and topics across Lattice.
This paper designs and evaluates persistent MPI RMA variants of Alltoallv, using fence and lock synchronization to separate initialization from execution. Benchmarks on LLNL's Dane supercomputer show that the fence-persistent variant outperforms the non-persistent baseline for large message sizes, achieving up to a 44% reduction in runtime. The study also evaluates algorithms under irregular sparse communication patterns and compares fence- and lock-based designs, clarifying trade-offs between synchronization methods.
Achieve up to 44% runtime reduction in MPI_Alltoallv by using persistent RMA, proving it a practical approach for HPC workloads with large messages.
Collective communication operations such as MPI_Alltoallv are central to many HPC applications, particularly those with irregular message sizes. We design, implement, and evaluate persistent MPI RMA variants of Alltoallv based on fence and lock synchronization, separating a one time initialization phase from per iteration execution to enable reuse of communication metadata and window state across repeated epochs. Our benchmarks tested on LLNL's Dane supercomputer show that the fence-persistent variant consistently outperforms the non-persistent baseline for large message sizes, achieving up to 44% reduction in runtime and improving scalability with increasing process counts; at 448 processes the runtime decreases from 2.49s to 1.54s (38% faster). We further evaluate the algorithms under irregular sparse communication patterns and compare fence- and lock-based designs, including hierarchical extensions. Message-size sweeps and a break-even model demonstrate that persistence provides immediate payoff for messages greater or equal to 32,768 bytes, while smaller messages show limited benefit due to metadata amortization costs. These results indicate that persistent RMA Alltoallv is a practical approach for workloads with large messages, where removing repeated metadata processing leaves runtime dominated by data movement, as evidenced by the increasing time savings with message size, and they clarify the trade-offs between fence and lock synchronization on modern HPC systems.