I'm building a decentralized ai marketplace and guess what? This piece of software is the backbone of our off-chain file transfer protocol. It just works; however, its seeder (BitTorrent-tracker) depends on node-webrtc, and it is not an official node package for web-rtc. It has some weird issues. For example, when you seed the torrent through BitTorrent-tracker, and on the client side (chrome browser), I used chrome://webrtc-internals to debug rtc connections. First time in my life, I coined the term connection leakage. A bug in the WebRTC handshake leads to too many connections (300+) for even 1kb torrents.
I hope it gets solved very soon.
I also attach my node profiling output. Looking for some advise if you have any..
[C++]:
ticks total nonlib name
5511 16.9% 43.2% epoll_pwait
692 2.1% 5.4% __pthread_cond_timedwait
682 2.1% 5.3% __lll_lock_wait
413 1.3% 3.2% __GI___pthread_mutex_lock
338 1.0% 2.6% __GI___pthread_mutex_unlock
128 0.4% 1.0% __write
84 0.3% 0.7% __pthread_cond_broadcast
83 0.3% 0.6% __lll_unlock_wake
62 0.2% 0.5% __mprotect
ticks total nonlib name
153 0.5% 1.2% JavaScript
8206 25.2% 64.3% C++
116 0.4% 0.9% GC
19811 60.8% Shared libraries
4411 13.5% Unaccounted
ticks cpp total name
692 27.3% 2.1% __pthread_cond_timedwait
679 26.8% 2.1% __lll_lock_wait
413 16.3% 1.3% __GI___pthread_mutex_lock
337 13.3% 1.0% __GI___pthread_mutex_unlock
100 3.9% 0.3% __write
84 3.3% 0.3% __pthread_cond_broadcast
82 3.2% 0.3% __lll_unlock_wake
52 2.1% 0.2% __mprotect