Difference between revisions of "Download Benchmarks"

From Sniper
Jump to navigation Jump to search
Line 14: Line 14:
 
This distribution currently contains the following benchmark suites:
 
This distribution currently contains the following benchmark suites:
 
* SPLASH-2
 
* SPLASH-2
* [http://parsec.cs.princeton.edu/ Parsec 2.1]
+
* [http://parsec.cs.princeton.edu/ PARSEC 2.1]
  
 
Usage example:
 
Usage example:

Revision as of 10:02, 19 February 2012

A package with benchmarks is available at sniper-benchmarks.tbz. These have been slightly adapted to:

  • 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

Options for run-sniper:

  • Make sure to define the GRAPHITE_ROOT (pointing to Sniper) and BENCHMARKS_ROOT (pointing to the location where sniper-benchmarks.tbz is installed)
  • Run run-sniper without any commandline options to see a list of supported benchmarks
  • -p suitename-benchmarkname (required): suite (splash2, parsec) and name (fft, barnes, ...) 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 -n passed 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 test, small and large are available, as defined in our IISWC 2011 paper.
  • -c, -g, -s: passed to sniper/run-sniper unmodified

This distribution currently contains the following benchmark suites:

Usage example: