README_traces.txt 2.59 KB
Newer Older
1 2 3 4
1- Download, build and install the DUMPI software according to the 
   instructions available at:
   http://sst.sandia.gov/about_dumpi.html

5 6
   Configure dumpi with the following parameters:

7
   ../configure --enable-test --disable-shared --prefix=/home/mubarm/dumpi/dumpi/install CC=mpicc CXX=mpicxx
8

9
2- Configure codes with DUMPI. Make sure the CC environment variable
10 11
   refers to a MPI compiler

12
   ./configure PKG_CONFIG_PATH=$PATH --with-dumpi=/path/to/dumpi/install
13 14
	 --prefix=/path/to/codes-base/install CC=mpicc 

15
3- Build codes-base (See codes-base INSTALL for instructions on building codes-base with dumpi)
16 17 18

    make clean && make && make install

19
4- Configure and build codes-net (See INSTALL for instructions on building codes-net).
20 21 22 23 24

5- Download and untar the design forward DUMPI traces from URL

   http://portal.nersc.gov/project/CAL/designforward.htm

25
----------------- RUNNING CODES MPI SIMULATION LAYER -----------------------
26
6- Download and untar the DUMPI AMG application trace for 216 MPI ranks using the following download link:
27

28 29
wget
http://portal.nersc.gov/project/CAL/doe-miniapps-mpi-traces/AMG/df_AMG_n216_dumpi.tar.gz
30

31
8- Configure model-net config file (For this example config file is available at
32
src/network-workloads/conf/modelnet-mpi-test-dfly-amg-216.conf)
33

34
9- Run the DUMPI trace replay simulation on top of model-net using:
35
   (/dumpi-2014.03.03.14.55.23- is the prefix of the DUMPI trace file. 
36
   We skip the last 4 digit prefix of the DUMPI trace files).
37

38
   ./src/network-workloads//model-net-mpi-replay --sync=1 
39 40 41
   --num_net_traces=216 --workload_file=/path/to/dumpi/trace/directory/dumpi-2014.03.03.15.09.03-  
   --workload_type="dumpi" --lp-io-dir=amg-216-trace --lp-io-use-suffix=1 
   -- ../src/network-workloads/conf/modelnet-mpi-test-dfly-amg-216.conf 
42 43 44

  The simulation runs in ROSS serial, conservative and optimistic modes.

45
   Note: Dragonfly and torus networks may have more number of nodes in the network than the number network traces (Some network nodes will only pass messages and they will not end up loading the traces). Thats why --num_net_traces argument is used to specify exact number of traces available in the DUMPI directory if there is a mis-match between number of network nodes and traces.
46

47 48
10- Running the simulation in optimistic mode 
    
49 50
    mpirun -np 4 ./src/network-workloads//model-net-mpi-replay --sync=3
    --num_net_traces=216 --workload_type="dumpi" --lp-io-dir=amg_216-trace
51 52
    --lp-io-use-suffix=1
    --workload_file=/projects/radix-io/mubarak/df_traces/directory/dumpi-2014.03.03.15.09.03- 
53
    -- src/network-workloads//conf/modelnet-mpi-test-dfly-amg-216.conf 
54