Engineering Supercomputing Platforms for Biomolecular Applications

TL;DR

This paper benchmarks various biomolecular software on diverse HPC hardware, highlighting the need for hardware diversity, challenges in data storage, and proposing strategies for better HPC system deployment and support.

Contribution

It provides a comprehensive performance and usability evaluation of biomolecular software across different HPC architectures, emphasizing the importance of hardware diversity and improved deployment practices.

Findings

GPUs are most efficient for biomolecular tasks

No single hardware suits all computational biology methods

Data storage remains a significant challenge

Abstract

A range of computational biology software (GROMACS, AMBER, NAMD, LAMMPS, OpenMM, Psi4 and RELION) was benchmarked on a representative selection of HPC hardware, including AMD EPYC 7742 CPU nodes, NVIDIA V100 and AMD MI250X GPU nodes, and an NVIDIA GH200 testbed. The raw performance, power efficiency and data storage requirements of the software was evaluated for each HPC facility, along with qualitative factors such as the user experience and software environment. It was found that the diversity of methods used within computational biology means that there is no single HPC hardware that can optimally run every type of HPC job, and that diverse hardware is the only way to properly support all methods. New hardware, such as AMD GPUs and Nvidia AI chips, are mostly compatible with existing methods, but are also more labour-intensive to support. GPUs offer the most efficient way to run most computational biology tasks, though some tasks still require CPUs. A fast HPC node running molecular dynamics can produce around 10GB of data per day, however, most facilities and research institutions lack short-term and long-term means to store this data. Finally, as the HPC landscape has become more complex, deploying software and keeping HPC systems online has become more difficult. This situation could be improved through hiring/training in DevOps practices, expanding the consortium model to provide greater support to HPC system administrators, and implementing build frameworks/containerisation/virtualisation tools to allow users to configure their own software environment, rather than relying on centralised software installations.