@@ -70,21 +70,20 @@ In this case the resulting `tor` binary can be found in `~/tor/src/app/tor` and
### TGen
OnionPerf uses TGen to generate traffic on client and server side for its measurements. Installing dependencies, cloning TGen to a subdirectory in the user's home directory, checking out version 0.0.1, and building TGen is done as follows:
OnionPerf uses TGen to generate traffic on client and server side for its measurements. Installing dependencies, cloning TGen to a subdirectory in the user's home directory, and building TGen is done as follows:
```shell
sudo apt install cmake libglib2.0-dev libigraph0-dev make
cd ~/
git clone https://github.com/shadow/tgen.git
cd tgen/
git checkout -b v0.0.1 v0.0.1
mkdir build
cd build/
cmake ..
make
```
The TGen binary will be contained in `~/tgen/build/tgen`, which is also the path that needs to be passed to OnionPerf's `--tgen` parameter when doing measurements.
The TGen binary will be contained in `~/tgen/build/src/tgen`, which is also the path that needs to be passed to OnionPerf's `--tgen` parameter when doing measurements.
### OnionPerf
...
...
@@ -281,7 +280,7 @@ The PDF output file contains visualizations of the following metrics:
The CSV output file contains the same data that is visualized in the PDF file. It contains the following columns:
-`transfer_id` is the identifier used in the TGen client logs which may be useful to look up more details about a specific measurement.
-`id` is the identifier used in the TGen client logs which may be useful to look up more details about a specific measurement.
-`error_code` is an optional error code if a measurement did not succeed.
-`filesize_bytes` is the requested file size in bytes.
-`label` is the data set label as given in the `--data/-d` parameter to the `visualize` mode.