6b845fd473
* refactor: modularize server-fixture * Update crates/server-fixture/server/Cargo.toml add newline Co-authored-by: sinu.eth <65924192+sinui0@users.noreply.github.com> * test: add browser benches * fix deps * ci: run ci workflow for all pull requests (#571) * misc fixes * fix clippy * don't log a non-critical error to stderr * use incognito (mitigates random hangs) * add notes * distinguish prover kind when plotting --------- Co-authored-by: sinu.eth <65924192+sinui0@users.noreply.github.com> Co-authored-by: Hendrik Eeckhaut <hendrik@eeckhaut.org> Co-authored-by: Ubuntu <ubuntu@ip-10-35-1-164.eu-central-1.compute.internal>
TLSNotary bench utilities
This crate provides utilities for benchmarking protocol performance under various network conditions and usage patterns.
As the protocol is mostly IO bound, it's important to track how it performs in low bandwidth and/or high latency environments. To do this we set up temporary network namespaces and add virtual ethernet interfaces which we can control using the linux tc (Traffic Control) utility.
Configuration
See the bench.toml file for benchmark configurations.
Preliminaries
To run the benchmarks you will need iproute2 installed, eg:
sudo apt-get install iproute2 -y
Running benches
Running the benches requires root privileges because they will set up virtual interfaces. The script is designed to fully clean up when the benches are done, but run them at your own risk.
Native benches
Make sure you're in the crates/benches/ directory, build the binaries, and then run the script:
cd binary
cargo build --release
sudo ./bench.sh
Browser benches
(Note, we recommend running browser benches inside a docker container (see docker.md) to avoid facing incompatibility issues observed in the latest versions of Chrome.)
With a Chrome browser installed on your system, make sure you're in the crates/benches/
directory, build the wasm module, build the binaries, and then run the script:
cd browser/wasm
rustup run nightly wasm-pack build --release --target web
cd ../../binary
cargo build --release --features browser-bench
sudo ./bench.sh
Metrics
After you run the benches you will see a metrics.csv file in the working directory. It will be owned by root, so you probably want to run
sudo chown $USER metrics.csv