|
|
@@ -27,6 +27,8 @@ Can run on a laptop (No special hardware requirements)
|
|
|
|
|
|
The results in the paper were computed using one [Intel Xeon Platinum 8380](https://www.intel.com/content/www/us/en/products/sku/212287/intel-xeon-platinum-8380-processor-60m-cache-2-30-ghz/specifications.html) CPU (80 threads; 40 cores @ 2.30 GHz, up to 3.40 GHz).
|
|
|
|
|
|
+We also tested the artifact on a laptop with a [13th Gen Intel Core i7-1360P](https://www.intel.com/content/www/us/en/products/sku/232155/intel-core-i71360p-processor-18m-cache-up-to-5-00-ghz/specifications.html) (16 threads; 4 performance cores, up to 5 GHz) and in a PETS artifact evaluation Standard VM allocated 4 threads from an [Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz](https://www.intel.com/content/www/us/en/products/sku/193957/intel-xeon-gold-6226-processor-19-25m-cache-2-70-ghz/specifications.html) CPU (2.70 GHz, up to 3.70 GHz).
|
|
|
+
|
|
|
### Software Requirements
|
|
|
|
|
|
Dependencies:
|
|
|
@@ -76,7 +78,7 @@ We used Docker version 29.1.3 with rust:1.93.0 as the base Docker image for our
|
|
|
|
|
|
### Estimated Time and Storage Consumption
|
|
|
|
|
|
-Running the artifact should take around 2 hours and requires around 15 GB of disk space.
|
|
|
+Running the artifact should take around 2–5 hours and requires around 15 GB of disk space.
|
|
|
|
|
|
## Environment
|
|
|
|
|
|
@@ -86,7 +88,7 @@ This artifact is available at https://git-crysp.uwaterloo.ca/vvecna/troll-patrol
|
|
|
|
|
|
### Set Up the Environment
|
|
|
|
|
|
-Time: 2 human-minutes + 6–11 compute-minutes
|
|
|
+Time: 2 human-minutes + 6–16 compute-minutes
|
|
|
|
|
|
```bash
|
|
|
git clone https://git-crysp.uwaterloo.ca/vvecna/troll-patrol-artifact.git
|
|
|
@@ -214,7 +216,7 @@ Our entire artifact can be run with the `./run.sh` script, which accepts the fol
|
|
|
|
|
|
This will run the setup script (if it has not already been run) and the scripts for both [Experiment 1](#experiment-1-lox-benchmarking) and [Experiment 2](#experiment-2-belarus-case-study), passing the arguments to those scripts as appropriate.
|
|
|
See [Experiment 1](#experiment-1-lox-benchmarking) for examples of using the `-n` and `-N` options.
|
|
|
-This process should take around 2 hours.
|
|
|
+This process should take around 2-5 hours.
|
|
|
(If the `--fast` option is used, the process should take around half an hour. See [Experiment 2](#experiment-2-belarus-case-study) for details.)
|
|
|
|
|
|
Alternatively, the scripts for the experiments can be run individually, as documented in the experiment descriptions below.
|
|
|
@@ -251,7 +253,7 @@ table-2-results.pdf and table-3-results.pdf can be used to verify Main Results [
|
|
|
|
|
|
#### Experiment 2: Belarus Case Study
|
|
|
|
|
|
-- Time: 1 human-minute + 1.5 compute-hours
|
|
|
+- Time: 1 human-minute + 1.5–4.5 compute-hours
|
|
|
|
|
|
```bash
|
|
|
./scripts/belarus.sh [--fast]
|
|
|
@@ -261,7 +263,7 @@ table-2-results.pdf and table-3-results.pdf can be used to verify Main Results [
|
|
|
|
|
|
The recommended way to run this script is without the `--fast` argument: `./scripts/belarus.sh`.
|
|
|
This will download 10 bridge extra-info archives from the Tor Project for the period of July 2020–April 2021, parse this data to learn daily connection counts from Belarus for each bridge, and then use Algorithms 1–3 to try to detect which bridges were blocked starting in late February 2021 and which were not.
|
|
|
-This takes about 1.5 hours.
|
|
|
+This takes about 1.5–4.5 hours.
|
|
|
|
|
|
If the `--fast` option is used, then the extra-info archives will not be downloaded from the Tor Project.
|
|
|
Instead, the script starts with a 6.7 MB archive (87 MB uncompressed) containing only the information we need.
|
