benchpark
benchpark copied to clipboard
LLNL
An open collaborative repository for reproducible specifications of HPC benchmarks and cross site benchmarking environments
This PR adds an mpi-only version of Laghos (https://github.com/CEED/Laghos) with a Sedov blast wave experiment. Although all of the experiments run successfully, FOM and success criteria are not working correctly....
Closes https://github.com/LLNL/benchpark/pull/178 Given an experiment that requests resources (nodes, cpus, gpus, etc.) and a system description (cpus-per-node, gpus-per-node, etc.) this intends to generate an appropriate scheduler request for resources. In...
This can come up when adding or modifying a benchmark - and the package.py is already in Spack, but not yet in Benchpark. - how to find the versions we...
Where should this live? - A sub-bullet under "Adding a Specific System configuration" - FAQ: I would like to use external dependencies ... Adding a Specific System could point here....
- Add function to call arch spec -- On my system, so I can add it to system spec in Benchpark -- (eventally) When creating a system spec in Benchpark...
Currently `benchpark setup` prints the spack concretization details in `/workspace/logs/setup..out` file. In case of multiple experiments, this concretization log appears only once per each set of experiments built using the...
https://flux-framework.readthedocs.io/projects/flux-core/en/latest/python/job_submission.html#job-manipulation Collaborators are doing similar things with Slurm.