Benchmark Overview

ModSim benchmarks are features, components, performance characteristics, or other properties that are important to the Laboratories.

ModSim Priority 1

Benchmark	Description	Language	Parallelism	Scale	Libraries
Kripke	Scalable 3D Sn deterministic particle transport code	C++	MPI+RAJA	Multi-node	RAJA, CHAI, Camp, Umpire
Laghos	LAGrangian High-Order Solver, unstructured high-order finite element compressible gas dynamics	C++	MPI+RAJA/CUDA/HIP	Multi-node	RAJA, MFEM, Hypre, Umpire
RAJA Performance Suite	Collection of loop-based computational kernels found in HPC applications	C++	MPI+RAJA /CUDA/HIP/OpenMP	Single node	RAJA
Branson	Implicit Monte Carlo transport	C++	MPI+CUDA/HIP	Multi-node	Umpire
Sparta	Direct Simulation Monte Carlo	C++	MPI+Kokkos	Multi-node	Kokkos

ModSim Priority 2

Benchmark	Description	Language	Parallelism	Scale	Libraries
AMG2023	AMG solver of sparse matrices	C	MPI+CUDA/HIP/SYCL OpenMP on CPU	Multi-node	Hypre, Umpire
LAMMPS ACE	Molecular dynamics using Atomic Cluster Expansion (ACE)	C++	MPI+Kokkos	Multi-node	Kokkos
Remhos	REMap High-Order Solver, unstructured high-order finite element advection	C++	MPI+RAJA/CUDA/HIP	Multi-node	RAJA, MFEM, Hypre
MiniEM	Electro-Magnetics solver	C++	MPI+Kokkos	Multi-node	Kokkos, Trillinos

Please note that half of the RAJA kernels are Priority 1, and the other half are Priority 2. Similarly, 2 of the Laghos problems are Priority 1, and the third is Priority 2.

Run Rules Synopsis

Source code modification categories:

1. Baseline: “out-of-the-box” performance

• Code modifications not permitted

• Compiler options can be modified, library substitutions permitted unless prohibited for a specific benchmark (see details on benchmark pages), problem decomposition may be changed

• If provided code cannot run on the proposed architecture as-is, limited source code modifications are permitted to port and tune for the target architecture using directives or commonly used interfaces.

2. Optimized: “speed of light”

• Aggressive code changes that enhance performance are permitted. Optimizations that will be applicable to mission applications are of more value.

• Algorithms fundamental to the program may not be replaced. Wholesale algorithm changes or manual rewriting of loops that become strongly architecture specific are of less value.

• The modified code must still pass validation tests.

• Optimizations will be reviewed by subject matter experts for applicability to the larger application portfolio and other goals such as performance portability and programmer productivity.

Priority 1

• 1. Kripke
• 2. Laghos
• 3. RAJA Performance Suite
• 4. Branson
• 5. SPARTA

Priority 2

• 1. AMG2023
• 2. LAMMPS ACE
• 3. RAJA Performance Suite
• 3. Remhos
• 4. MiniEM

MPI Benchmarks

• 1. Phloem
• 2. OSU Microbenchmarks
• 3. Sandia Microbenchmarks - Message rate