Home My Page Projects Code Snippets Project Openings diderot
Summary Activity Tracker Tasks SCM

SCM Repository

[diderot] Annotation of /benchmarks/README
ViewVC logotype

Annotation of /benchmarks/README

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1932 - (view) (download)

1 : jhr 1574 Instructions for the Diderot benchmark suite.
2 :    
3 :     ===============
4 :     PREREQUISITES
5 :     ===============
6 :    
7 :     You must have Diderot and TEEM installed. See the Diderot INSTALL instructions for
8 :     more details.
9 :    
10 :     ===============
11 :     CONFIGURATION
12 :     ===============
13 :    
14 :     Run autoconf:
15 :    
16 :     % autoconf -Iconfig
17 :    
18 :     To configure the benchmark tree you will need to provide both a path to the TEEM
19 :     installation and a path to the Diderot compiler (diderotc). The invocation will
20 :    
21 :     % ./configure --with-teem=/path/to/teem --with-diderotc=/path/to/diderotc
22 :    
23 :     where "/path/to/teem" is the full path of the directory
24 :     containing the "lib" and "include" directories containing
25 :     "libteem.{a,so,dylib}" and "teem/*.h", respectively.
26 :    
27 :     ===============
28 :     INSTALLATION
29 :     ===============
30 :    
31 :     TBA
32 :    
33 :     ===============
34 : jhr 1577 RUNNING BENCHMARKS
35 :     ===============
36 :    
37 :     To run a benchmark, use the command
38 :    
39 : jhr 1932 % ./scripts/run-one.sh bmark nruns nprocs nworkers
40 : jhr 1577
41 :     from the root of the benchmark tree. The command-line arguments are
42 :    
43 : jhr 1932 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 : jhr 1577
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 : jhr 1574 ADDING BENCHMARKS
60 :     ===============
61 :    
62 :     Adding a benchmark is straightforward. Create a directory for the benchmark in the
63 :     benchmarks/programs directory. Any required data files should be placed in the
64 :     benchmarks/data directory. The benchmark should have two source files with the
65 :     names
66 :    
67 :     bmark-teem.c The TEEM version implemented in C
68 :     bmark-diderot.diderot The Diderot version
69 :    
70 :     Each benchmark has a Makefile, but these are generated as part of the configuration
71 :     process, so once a bencmark has been added you will need to rerun configure.

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0