Talk:Performance: Difference between revisions
From Biowerkzeug Wiki
Jump to navigationJump to search
Line 13: | Line 13: | ||
Note: | Note: | ||
* only run this on an empty machine: we are using ''wall time'' for timing | * only run this on an empty machine: we are using ''wall time'' for timing | ||
Slightly more sophisticated: use [[test_scaling.py]]. | |||
cd testjobs | |||
test_scaling.py ''NSLOTS'' | |||
where ''NSLOTS'' is the maximum number of available cpus/cores. Results are the files | |||
scaling.xvg # numbers | |||
scaling.png # graphs |
Revision as of 15:23, 7 December 2008
Integration with tests
We could write a script that does the benchmark while running the test. It would even be possible to automatically post it (with the user's consent, of course). — Oli 16:03, 14 November 2008 (UTC)
Scaling
Use updated calc_testjobs_linux.sh
DATA=scaling.xvg echo -e "# scaling for Hippo\n# numthreads walltime/s" > $DATA for NSLOTS in `seq 8`; do echo "-- NSLOTS = $NSLOTS"; ../../calc_testjobs_linux.sh -n $NSLOTS walp_octane_NPT_sp_MD \ | awk '/BENCHMARK/ {print $3, $4}' >> $DATA; done
Note:
- only run this on an empty machine: we are using wall time for timing
Slightly more sophisticated: use test_scaling.py.
cd testjobs test_scaling.py NSLOTS
where NSLOTS is the maximum number of available cpus/cores. Results are the files
scaling.xvg # numbers scaling.png # graphs