SCM Repository
Diff of /benchmarks/README
Parent Directory
|
Revision Log
|
Patch
revision 1574, Sat Oct 29 14:49:18 2011 UTC | revision 1932, Wed Jun 27 12:48:08 2012 UTC | |
---|---|---|
# | Line 31 | Line 31 |
31 | TBA | TBA |
32 | ||
33 | =============== | =============== |
34 | RUNNING BENCHMARKS | |
35 | =============== | |
36 | ||
37 | To run a benchmark, use the command | |
38 | ||
39 | % ./scripts/run-one.sh bmark nruns nprocs nworkers | |
40 | ||
41 | from the root of the benchmark tree. The command-line arguments are | |
42 | ||
43 | bmark -- the name of the benchmark program (i.e., its directory name) | |
44 | nruns -- the number of runs of each instance | |
45 | nprocs -- the maximum number of processors for the parallel versions; | |
46 | specifying 0 will omit the parallel tests. | |
47 | nworkers -- max number of workers/CU for GPU version (0 means no GPU run) | |
48 | ||
49 | Running this script will produce two files. | |
50 | ||
51 | bmark-report.date | |
52 | bmark-log.date | |
53 | ||
54 | (where "bmark" is the name of the benchmark and "date" is a timestamp). The | |
55 | report file contains the timing results, while the log file contains the | |
56 | transcript of the build process. | |
57 | ||
58 | =============== | |
59 | ADDING BENCHMARKS | ADDING BENCHMARKS |
60 | =============== | =============== |
61 |
|
root@smlnj-gforge.cs.uchicago.edu | ViewVC Help |
Powered by ViewVC 1.0.0 |