mirrors/arti.git/tests/chutney/arti-bench.sh, branch arti-v0.0.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.42021-12-21T14:54:16Zarti-bench.sh: Handle the case where CHUTNEY_PATH is set.2021-12-21T14:54:16ZNick Mathewsonnickm@torproject.org2021-12-21T14:53:13Zurn:sha1:032b0d2575cfdabc0cfafb164968808372f5f082
Previously, this case would cause arti-bench to hang forever, trying
to bootstrap against one network while another network was running.
arti-bench.sh: set $RUST_LOG if it isn't set.2021-12-21T14:54:16ZNick Mathewsonnickm@torproject.org2021-12-21T14:35:21Zurn:sha1:ba6828d9fe49565eaca433e9a40d296c72fda43e
(An empty $RUST_LOG no output, and confuse the nickm^Wuser.)
Introduce an experimental benchmarking utility for Arti2021-12-16T16:12:59Zetator@eta.st2021-12-14T17:29:04Zurn:sha1:06a94288caa6cdb61d90982f171b7da688951b6b
The new `arti-bench` crate does a simple end-to-end benchmark test
embedding Arti: it generates some random data (of configurable amount,
depending on command-line parameters), and then sends said data back and
forth via Arti (which should be configured to use a local Chutney
network).
Additionally, the benchmark can also be run via a local SOCKS5 server
(in order to benchmark the performance via a local Chutney node, for
comparison).
The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as
required to make this work.
This is very much a first cut; there are many things that should
eventually get added, such as support for multiple connections, JSON
output capabilities, running multiple tests, ...