|
|
@@ -8,17 +8,12 @@ Dependencies:
|
|
|
- bash
|
|
|
- docker
|
|
|
- git
|
|
|
-- numactl
|
|
|
-
|
|
|
-We use numactl to isolate each experiment to a single thread. If you do
|
|
|
-not want to install numactl, you can still run the script, but this may
|
|
|
-affect the results.
|
|
|
|
|
|
To reproduce our results:
|
|
|
|
|
|
1. `git clone -b artifact https://git-crysp.uwaterloo.ca/vvecna/lox-troll-patrol-extension`
|
|
|
2. `cd lox-troll-patrol-extension`
|
|
|
-3. `./run.sh [-n NUM_PERFORMANCE_CORES]` or `./run-fast.sh [-n NUM_PERFORMANCE_CORES]`
|
|
|
+3. `./run.sh [-n NUM_PERFORMANCE_CORES] [-N PERFORMANCE_CORE_RANGE]` or `./run-fast.sh [-n NUM_PERFORMANCE_CORES] [-N PERFORMANCE_CORE_RANGE]`
|
|
|
|
|
|
**The `./run.sh` script takes a long time and requires a few GB of free
|
|
|
space.** The reason is that it downloads and processes all extra-info
|
|
|
@@ -39,7 +34,12 @@ will take. The choice between the two scripts only determines whether
|
|
|
other steps are pretty quick. If you specify `-n NUM_PERFORMANCE_CORES`,
|
|
|
then the Lox benchmarking step (`./scripts/generate-lox-results.sh`)
|
|
|
will only use the first `NUM_PERFORMANCE_CORES` threads. This may take a
|
|
|
-bit longer but should ensure that the results are computed fairly.
|
|
|
+bit longer but should ensure that the results are computed fairly. You
|
|
|
+can also specify `-N PERFORMANCE_CORE_RANGE` to use only specific
|
|
|
+threads (e.g., `-N 1-2,4-5`), instead of 0 through
|
|
|
+`NUM_PERFORMANCE_CORES`-1. If you use the `-N` option, please also use
|
|
|
+the `-n` option to specify how many threads are available in the
|
|
|
+specified set.
|
|
|
|
|
|
## Results
|
|
|
|
