REVIEW 2 cited by
Application-Driven Exascale: The JUPITER Benchmark Suite
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
Benchmarks are essential in the design of modern HPC installations, as they define key aspects of system components. Beyond synthetic workloads, it is crucial to include real applications that represent user requirements into benchmark suites, to guarantee high usability and widespread adoption of a new system. Given the significant investments in leadership-class supercomputers of the exascale era, this is even more important and necessitates alignment with a vision of Open Science and reproducibility. In this work, we present the JUPITER Benchmark Suite, which incorporates 16 applications from various domains. It was designed for and used in the procurement of JUPITER, the first European exascale supercomputer. We identify requirements and challenges and outline the project and software infrastructure setup. We provide descriptions and scalability studies of selected applications and a set of key takeaways. The JUPITER Benchmark Suite is released as open source software with this work at https://github.com/FZJ-JSC/jubench.
Forward citations
Cited by 2 Pith papers
-
Introducing Milabench: Benchmarking Accelerators for AI
Mila releases Milabench, a 42-benchmark open-source suite, and shows that for real AI workloads the NVIDIA H100 generally outperforms AMD MI300X and Intel Gaudi2 despite MI300X's high synthetic FLOP counts.
-
Energy-aware operation of HPC systems in Germany
This review of eight German HPC centers concludes that a combination of cooling, scheduling, monitoring, and hardware choices is required to meaningfully reduce energy use.
Discussion (0). Continue with ORCID to comment.