Commit 9b04b7c5 authored by Belviranli, Mehmet E's avatar Belviranli, Mehmet E
Browse files

Update README.md

parent 1ee9b89d
......@@ -40,7 +40,6 @@ applications (both baseline and Juggler-integrated version) can be
accessed via the following (this) repository:
``` {.bash language="bash"}
https://code.ornl.gov/fub/juggler
```
......@@ -66,7 +65,7 @@ Installation
Clone Juggler runtime and application suite from the git repo:
``` {.bash language="bash"}
$ git clone git@code.ornl.gov:fub/juggler.git
$ git clone https://code.ornl.gov/fub/juggler.git
$ JUGGLER_HOME=$(pwd)/juggler
```
......@@ -112,7 +111,6 @@ combine the values from all runs in a *tab separated value* format.
$ bash exp 1 output execTime 2 formattedResults1.csv
```
\medskip
Parsed values will be written into `formattedResults1.csv`, in a
tabular format. There will be 7 columns in total, one for each
application. The number of rows in the csv file will be equal to
......@@ -127,13 +125,18 @@ combine the values from all runs in a *tab separated value* format.
$ bash exp 1 output check 2 formattedResults2.csv
```
The parsed output will be written into `formattedResults2.csv` file,
and the values will be either SUCCESS or FAIL.
The parsed output will be written into `formattedResults2.csv` file,
and the values will be either SUCCESS or FAIL. Please note that, since
serial execution takes too long, the verification runs are only once per
each applciation, even if multiple (i.e. 5) runs are specified.
3. **To parse task load deviations** (i.e. Figure 5), run:
3. **To parse task load deviations** , which is the data used to draw
Figure 5), run:
``` {.bash language="bash"}
$ bash exp 1 output avgTaskLoad 2 formattedResults3.csv
$ bash exp 1 output minTaskLoad 2 formattedResults3.csv
$ bash exp 1 output maxTaskLoad 2 formattedResults3.csv
```
......@@ -142,7 +145,7 @@ Experiment customization
**Number of runs** for each type of run in the main experiment can be
modified by changing the input parameters of `exp` script, as explained
in A.4.
above.
Additionally, if only specific subset of applications is desired to be
tested, the values in the bash array, named `$APPS`, in the `exp` script
......@@ -159,8 +162,12 @@ the *key string* and *column number* to the value parser (i.e. *\"exp
``` {.bash language="bash"}
$ bash exp 1 output.PROF write_sector_misses 7 formatted.tsv
```
Please note that, profiling runs take longer to execute, and sometimes
may not run to completion, due to the fact that nvprof does not play
nice with the persistent threads approach that Juggler uses.
2. Host runtime and inspection loop overhead breakdown:
2. Host runtime and inspection loop overhead breakdown:
``` {.bash language="bash"}
$ bash exp 1 output initAppContext_H 2 formatted.tsv
......@@ -170,12 +177,16 @@ the *key string* and *column number* to the value parser (i.e. *\"exp
$ bash exp 1 output buildCSR 2 formatted.tsv
```
3. Total application runtime, including user data initialization and
3. Total application runtime, including user data initialization and
transfers:
``` {.bash language="bash"}
$ bash exp 1 output totalTime 2 formatted.tsv
```
Please note that this data includes large data transfers that exist in
both Juggler and baseline. Therefore, timings obtained via this method
does not accurately represent benefits of Juggler.
**Compiling & Running single application:** In our test suite,
......@@ -199,7 +210,7 @@ parameters (e.g. scheduling policy) are changed.
$ ./OMP_CUDART -n {matrix_size} -b {block_size} -d {1|2} [-c]
```
The `-d` parameter indicates the run mode, which is 1 for Juggler,
The `-d` parameter indicates the run mode, which is 1 for Juggler,
and 2 for global barriers. The optional `-c` parameter enables
verification against serial version and compares the two outputs.
`-c` is enabled by default.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment