Revision as of 13:22, 12 October 2012 by Tcarlson
- Build using the compilation switches that Sniper requires (e.g. -mno-sse4), see Porting applications to Sniper.
- Mark the start and end of the parallel section (region of interest, ROI), see Simulator hooks.
- Runner scripts to automatically run a benchmark in Sniper with the right command-line options for a predefined collection of input sets
- Make sure to define the GRAPHITE_ROOT (pointing to Sniper) and BENCHMARKS_ROOT (pointing to the location where sniper-benchmarks.tbz is installed)
run-sniperwithout any commandline options to see a list of supported benchmarks
-p suitename-benchmarkname(required): suite (splash2, parsec) and name (fft, blackscholes, ...) of the benchmark
-n numcores(required): number of threads to run. Note that this is the total number of threads that will run (equal to the number of available cores in the simulated machine). For Parsec, this means that the
-npassed to the benchmark is usually lower since many Parsec programs start additional helper threads or use multiple threads per requested core.
-i inputsize(required): input set name. Usually
largeare available, as defined in our IISWC 2011 paper.
-s: passed to
This distribution currently contains the following benchmark suites:
- PARSEC 2.1
- wget http://snipersim.org/packages/sniper-benchmarks.tbz
- tar xjf sniper-benchmarks.tbz
- # or
- git clone http://snipersim.org/git/benchmarks.git
- cd benchmarks
- export GRAPHITE_ROOT=/path/to/sniper
- export BENCHMARKS_ROOT=$(pwd)
- ./run-sniper -p splash2-fft -i test -n 4 -c gainestown
- # or
- ./run-sniper --benchmarks=splash2-fft-test-4 -c gainestown
- # or
- ./run-sniper --benchmarks=splash2-fft-test-1,splash2-fft-test-1,splash2-fft-test-1,splash2-fft-test-1 -c gainestown