Claude H. (Rusty) Davis Iv
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Claude H. (Rusty) Davis Iv has a total of 13 co-authors. Here are the top co-authors by number of shared publications:
- Ashlyn Lee
High Performance Computing Division, Los Alamos National Laboratory, United States of America and Colorado State University, United States of America
1 shared publication - Benjamin Stormer
High Performance Computing Division, Los Alamos National Laboratory, United States of America and U. Texas at Austin, United States of America
1 shared publication - Jake Tronge
Kent State University, Kent, OH, USA
1 shared publication - Jieyang Chen
University of Oregon, Eugene, OR, USA
1 shared publication - Jordan Ogas
High Performance Computing Division, Los Alamos National Laboratory, United States of America
1 shared publication - Patricia Grubel
Los Alamos National Laboratory, Los Alamos, NM, USA
1 shared publication
Latest Publications
- 29 November 2023
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Services Computing
- Vol. 17 (1) , 156-168
An HPC-Container Based Continuous Integration Tool for Detecting Scaling and Performance Issues in HPC Applications
Testing is one of the most important steps in software development–it ensures the quality of software. Continuous Integration (CI) is a widely used testing standard that can report software quality to the developer in a timely manner during development progress. Performance, especially scalability, is another key factor for High Performance Computing (HPC) applications. There are many existing profiling and performance tools for HPC applications, but none of these are integrated into CI tools. In this work, we propose BeeSwarm, an HPC container based parallel scaling performance system that can be easily applied to the current CI test environments. BeeSwarm is mainly designed for HPC application developers who need to monitor how their applications can scale on different compute resources. We demonstrate BeeSwarm using three different HPC applications: CoMD, LULESH and NWChem. We utilize GitHub Actions and provision resources from Google Compute Engine. Our results show that BeeSwarm can be used for scalability and performance testing of a variety of HPC applications, allowing developers to monitor application performance over time.
- 29 November 2023
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Services Computing
- Vol. 17 (1) , 156-168
An HPC-Container Based Continuous Integration Tool for Detecting Scaling and Performance Issues in HPC Applications
Testing is one of the most important steps in software development–it ensures the quality of software. Continuous Integration (CI) is a widely used testing standard that can report software quality to the developer in a timely manner during development progress. Performance, especially scalability, is another key factor for High Performance Computing (HPC) applications. There are many existing profiling and performance tools for HPC applications, but none of these are integrated into CI tools. In this work, we propose BeeSwarm, an HPC container based parallel scaling performance system that can be easily applied to the current CI test environments. BeeSwarm is mainly designed for HPC application developers who need to monitor how their applications can scale on different compute resources. We demonstrate BeeSwarm using three different HPC applications: CoMD, LULESH and NWChem. We utilize GitHub Actions and provision resources from Google Compute Engine. Our results show that BeeSwarm can be used for scalability and performance testing of a variety of HPC applications, allowing developers to monitor application performance over time.
- Open Access
- 12 November 2023
- Published by Association for Computing Machinery (ACM)
- p. 135-146
Charliecloud’s layer-free, Git-based container build cache
A popular approach to deploying scientific applications in high performance computing (HPC) is Linux containers, which package an application and all its dependencies as a single unit. This image is built by interpreting instructions in a machine-readable recipe, which is faster with a build cache that stores instruction results for re-use. The standard approach (used e.g. by Docker and Podman) is a many-layered union filesystem, encoding differences between layers as tar archives. We describe a new approach, implemented in Charliecloud: store changing images in a Git repository. Our experiments show this performs similarly to layered caches on both build time and disk usage, with a considerable advantage for many-instruction recipes. Our approach also has structural advantages: better diff format, lower cache overhead, and better file de-duplication. These results show that a Git-based cache for layer-free container implementations is not only possible but may outperform the layered approach on important dimensions.
- 12 November 2023
- Published by Association for Computing Machinery (ACM)
- p. 135-146
Open AccessCharliecloud’s layer-free, Git-based container build cache
A popular approach to deploying scientific applications in high performance computing (HPC) is Linux containers, which package an application and all its dependencies as a single unit. This image is built by interpreting instructions in a machine-readable recipe, which is faster with a build cache that stores instruction results for re-use. The standard approach (used e.g. by Docker and Podman) is a many-layered union filesystem, encoding differences between layers as tar archives. We describe a new approach, implemented in Charliecloud: store changing images in a Git repository. Our experiments show this performs similarly to layered caches on both build time and disk usage, with a considerable advantage for many-instruction recipes. Our approach also has structural advantages: better diff format, lower cache overhead, and better file de-duplication. These results show that a Git-based cache for layer-free container implementations is not only possible but may outperform the layered approach on important dimensions.