From 96c5775eccd3c371071e63470164b645a9c4e65b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20Frosteg=C3=A5rd?= Date: Thu, 18 Nov 2021 22:51:19 +0100 Subject: [PATCH] Update README --- README.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 528dad1..36bb593 100644 --- a/README.md +++ b/README.md @@ -25,8 +25,8 @@ of sub-implementations for different protocols: - Install Rust with [rustup](https://rustup.rs/) (stable is recommended) - Install cmake with your package manager (e.g., `apt-get install cmake`) -- Unless you're planning to only run aquatic_udp and only the cross-platform, - mio based implementation, make sure locked memory limits are sufficient. +- Unless you're planning to only run the cross-platform mio based + implementations, make sure locked memory limits are sufficient. You can do this by adding the following lines to `/etc/security/limits.conf`, and then logging out and back in: @@ -118,8 +118,7 @@ except that it: source IP is always used. * Doesn't track of the number of torrent downloads (0 is always sent). -Supports IPv4 and IPv6 (BitTorrent UDP protocol doesn't support IPv6 very well, -however.) +Supports IPv4 and IPv6. #### Performance @@ -130,6 +129,12 @@ More details are available [here](./documents/aquatic-udp-load-test-2021-11-08.p Since making this benchmark, I have improved the mio-based implementation considerably and removed the glommio-based implementation. +#### Optimisation attempts that didn't work out + +* Using glommio +* Using io-uring +* Using zerocopy + vectored sends for responses + ### aquatic_http: HTTP BitTorrent tracker [HTTP BitTorrent protocol]: https://wiki.theory.org/index.php/BitTorrentSpecification#Tracker_HTTP.2FHTTPS_Protocol