Automatic Cache Purge vs. Static Binary Set for Spack Buildcache in Low‑Traffic HPC Workloads
The goal is to minimize compute and network costs for a low‑traffic HPC workload by leveraging Spack’s binary cache (buildcache) and local mirror. When the binary cache is populated, administrators must decide whether to let Spack automatically purge old spec entries or to maintain a static set of binaries that persists across package variant changes or upst