stun VS aquatic

This isn't true.

In 2017 appear.in published some numbers. They saw ~15% were not able to do P2P. https://medium.com/@fippo/what-kind-of-turn-server-is-being-...

Reading your stackoverflow link my guess is that you aren't using STUN. A P2P connection can't be established without a NAT hole punch.

Also if possible I would avoid the terms `Full-cone NAT` and `Symmetric NAT` they don't do a good job of describing what is actually happening. NAT Mapping/NAT Filtering is the best way to describe it. I wrote a little bit about it here [0]. To see what type of NAT you have try stun-nat-behaviour[1]

[0] https://webrtcforthecurious.com/docs/03-connecting/#nat-mapp...

[1] https://github.com/pion/stun/tree/master/cmd/stun-nat-behavi...

If you test your NAT on the destination via a tool like https://github.com/pion/stun/tree/master/cmd/stun-nat-behaviour, what does it report for mapping and filtering?

How does Bitmagnet compare to Aquatic? https://github.com/greatest-ape/aquatic

I have a question on UnsafeCell usage that popped up while implementing io_uring support for aquatic_udp. I find the docs slightly confusing (in particular the part that I've marked in bold):

I've done a new round of benchmarking of open UDP BitTorrent tracker implementations. Results were great for aquatic_udp, achieving double the throughput of opentracker when running on 8 CPU cores:

If you run your tracker on Linux and an info hash whitelist approach would work for your use case, it might be worthwhile having a look at aquatic_ws [0]. It relies on tungstenite [1] for websockets and achieves around 20x the throughput of the reference implementation when running with four threads.

[0] https://github.com/greatest-ape/aquatic

aquatic, a multithreaded BitTorrent tracker with world-leading performance

But aquatic_udp doesn't use glommio.. https://github.com/greatest-ape/aquatic/pull/29

aquatic is a Apache 2.0-licensed BitTorrent tracker written in Rust that I have developed over the last couple of years. It focuses on correctness, stability and high performance.

The udp request parsing code seems to have been copied from aquatic. Please note that the Apache 2.0 license requires attribution.