- choosing different rsults dir allows to run the same benchmark more than once to have more than one measure - this makes `hibenchonphysix.py` more decoupled from hibench, in the hope that it will be completely unaware of hibench at some poing (therefore reusable with other benchmarks) |
||
|---|---|---|
| .. | ||
| hibenchonphysix.py | ||
| readme.md | ||
| showresults.py | ||
| starbench-template.job | ||
readme.md
This example illustrates how starbench is used at IPR (Institut de Physique de Rennes) to measure the performance of hibridon on IPR's cluster (physix)
usage:
graffy@physix-frontal:/opt/ipr/cluster/work.global/graffy/starbench$ ./hibenchonphysix.py --commit-id 53894da48505892bfa05693a52312bacb12c70c9 --results-dir $GLOBAL_WORK_DIR/graffy/hibridon/benchmarks/starbench/hibench/2024-10-07-16:00:00
hibenchonphysix.py script launches two sge jobs for each machine type in physix cluster:
- one job that performs a benchmark of hibridon with
gfortrancompiler - one job that performs a benchmark of hibridon with
ifortcompiler
When the job successfully completes, it puts the results of the benchmark on physix's global work directory (eg /opt/ipr/cluster/work.global/graffy/hibridon/benchmarks/starbench/53894da48505892bfa05693a52312bacb12c70c9/nh3h2_qma_long/intel_xeon_x5550/gfortran)