Implementations are quite IO-bound and spend a lot of their time reading fromĪnd writing to sockets. Starting more socket_workers than request_workers is recommended. target/release/aquatic_ws -c "aquatic-ws-config.toml " Configuration values target/release/aquatic_http -c "aquatic-http-config.toml ". target/release/aquatic_udp -c "aquatic-udp-config.toml ". Note that both aquatic_http and aquatic_ws require configuring TLSĬertificate and private key files. (listening address) under the network section. target/release/aquatic_ws -p > "aquatic-ws-config.toml " target/release/aquatic_http -p > "aquatic-http-config.toml " They come with comments and differ between protocols./target/release/aquatic_udp -p > "aquatic-udp-config.toml " etc/security/nf, and then logging out and back in: * hard memlock 512 * soft memlock 512 You can do this by adding the following lines to Unless you're planning to only run aquatic_udp, make sure locked memory scripts /env -native -cpu -without -avx - 512 # recommended for the other implementations. Install cmake with your package manager (e.g., apt-get install cmake)Ĭompile the implementations that you are interested in: # Tell Rust to enable support for all CPU extensions present on current CPU # except for those relating to AVX - 512. Install Rust with rustup (stable is recommended) Of sub-implementations for different protocols: Name SLoC aquatic: high-performance BitTorrent trackerīlazingly fast, multi-threaded BitTorrent tracker written in Rust, consisting
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |