Joakim Frostegård fe5ccf6646 ws: refactor, bug fixes, improvements (#155)
- split swarm worker into two modules
- split socket worker into two modules
- keep track of which offers peers have sent and only allow matching
answers
- always clean up after closing connection
- use channel for telling connections to close
- move some logic into new ConnectionRunner struct
- use slotmap for connection reference storage
- fix double counting of error responses
- actually close connections that take too long to send responses to
- remove announced_info_hashes entry on AnnounceEvent::Stopped
2023-11-09 18:06:21 +01:00
2023-02-04 18:28:28 +01:00
2023-01-26 21:12:21 +01:00
2023-08-28 23:39:30 +02:00
2022-07-23 17:50:54 +02:00
2023-10-18 23:53:41 +02:00

aquatic: high-performance open BitTorrent tracker

CI

High-performance open BitTorrent tracker, consisting of sub-implementations for different protocols:

Name Protocol OS requirements
aquatic_udp BitTorrent over UDP Unix-like
aquatic_http BitTorrent over HTTP over TLS Linux 5.8+
aquatic_ws WebTorrent, optionally over TLS Linux 5.8+

Features at a glance:

  • Multithreaded design for handling large amounts of traffic
  • All data is stored in-memory (no database needed)
  • IPv4 and IPv6 support
  • Supports forbidding/allowing info hashes
  • Prometheus metrics
  • Automated CI testing of full file transfers

Known users:

Performance of the UDP implementation

UDP BitTorrent tracker throughput comparison

More benchmark details are available here.

Usage

Please refer to the README pages for the respective implementations listed in the table above.

Architectural overview

Architectural overview of aquatic

Copyright (c) 2020-2023 Joakim Frostegård

Distributed under the terms of the Apache 2.0 license. Please refer to the LICENSE file in the repository root directory for details.

Trivia

The tracker is called aquatic because it thrives under a torrent of bits ;-)

Languages
Rust 96.5%
Shell 2%
HTML 1.2%
Dockerfile 0.3%