Follow

It look like the major (open-source) torrent clients are pretty old projects. Only qBT is still in very active development, the others are on life support

· · Web · 2 · 3 · 7

They are somewhat stable and feature complete, so there is that. But there are still many bugs if you go through the issues. Most of them will probably never get fixed

In my experience, Deluge and Transmission don't scale really well with a high number of torrents/active peers.

rTorrent is better, but I'm not that impressed, since there is now queuing system, many active torrents it slows down a lot. I have to stop torrents in order to get proper download speeds. Also the XMLRPC requests can be very slow when rTorrent is under load

I'm trying qBT on a big machine and it seems to handle things much better no slowdown of the API under load, proper down/up speeds even with many torrents, and a queuing system.

I'm currently seeing ~200 torrents at ~1Gbps with ~1k connection, which is impressive

transmission would have been dead by now

the web UI of qBT is extremely ugly, but it gets the job done and is great performance-wise.

The Flood fork supports qBT. But with many torrents, it is very sluggish. Also it doesn't support qBT categories, only tags/labels

Also, qBT make better use of the CPU it seems.

It can also do hash checking on multiple torrents at once! When I tried it, it used all of the CPU and the I/O, which is great, better than waiting forever to check each torrent on by one (IMO)

My actual seedbox has a massive CPU, but it's barely used by rTorrent (and Transmission before that), which is quite sad.

I should probably tweak some sysctl stuff to handle more connections, but I don't know enough about that

(I'm downloading on a 1TB block storage volume, hence the iowait)

ok so I moved all my torrents from rTorrent to qBT on my actual seedbox, it's night and day

it's much faster, the web UI/API doesn't struggle a bit

I only bumped the async i/o threads to 32 (from 10) because I have 32 cores. I uses more RAM (~8 GB) but I have 96 so it's fine...

I'll see how qBT does over the span of a couple of days, but for now it's much better than everything I used before in terms of performance

Transmission seem to use threads, but not has extensively has qBT.

This doesn't matter for light usage, but on a big dedicated server and hundreds of torrents, it's another story

"asynchronous disk I/O" by the dev of libtorrent (the one used by qBT, not the rTorrent one) in 2012: blog.libtorrent.org/2012/10/as

@angristan perhaps
sysctl -w net.netfilter.nf_conntrack_max=1048576
echo 262144 > /sys/module/nf_conntrack/parameters/hashsize
sysctl -w net.core.rmem_max=851968
sysctl -w net.core.wmem_max=851968

@angristan you are doing distributed block storage over torrent or what?

@angristan

Thank you for the analysis. You've inspired me to check out qbitorrent as an alternative to deluge. :D

@angristan
There is also a plugin based search engine ;)

@angristan Intéressante comparaison.

J'utilise rTorrent simplement par habitude depuis des années mais je déteste son développement. J'ai moi-même été victime de problèmes que j'ai dû résoudre de façon non-orthodoxe en attendant la prochaine release.

Pour Flood : que veux-tu dire par sluggish ? Le scroll est pas hyper smooth (et bizarrement sur iPad nickel) mais en dehors de ça c'est OK.

@wonderfall je suis plus optimiste sur le futur de qBT que de rTorrent...

Oui pour Flood le scroll est assez laborieux, et la tab me prends pas mal de CPU. Peut-être qu'avec un Macbook M1 ça serait mieux du coup :blobderpy:

@angristan Have you tried deluge? Their native client supports remote connections and handles my 500 torrents pretty well

@angristan I use Transmission and it’s extremely hit and miss, sometimes I find I have to keep restarting the application to make it pick up peers, other times it “just works” and gets good speeds. I’ll give qBittorrent a go for a bit and see what it’s like. I’ve just used Transmission since forever and become loyal to what I know out of habit. Also, other clients seem to have way more cluttered UI’s whereas Transmission is clean like uTorrent back in the good old days.

@aspie4K on my desktop, I also use Transmission. It's simple and reliable

@angristan ah I you’re talking about seedboxes. I have found the quality of the network on a seedbox is far far more of an influence on performance than the choice of client. I got seedboxes from two providers both using Transmission, one was blazing fast, picked up many peers, handled 200+ active torrents like a breeze. The other performed mostly slower than my home connection.

@aspie4K I make my own seedbox on a dedicated sever, so I can compare apples to apples

@angristan that’s awesome, where’s it running from? I’ve considered self-hosting a seedbox but it’s hard to find a good host who will allow it.

@aspie4K In Europe there are many providers suitable for that, Scaleway, Hetzner, OVH and more

@angristan oh I’ve used Hetzner to run a VPN before so I’m familiar with them. Thanks for the recommendations!

@angristan @aspie4K Isn't Hetzner really sensitive when it comes to copyright and abuse claims?

@alex @angristan I have limited experience with it to be honest, never had issues running a VPN through it. But I had no problem running a VPN through AWS either. Both occasions I torrented fairly often.

@alex @angristan I can tell you Digital Ocean is very sensitive to that stuff, any DMCA claim they get they send you a warning, three and they ban you.

@angristan @alex wish I could get into some decent private trackers, I miss What.cd.

@aspie4K @angristan @alex there's redacted and they have an interview process, it's not hard to get into if you're a music enthusiast. see here: https://interviewfor.red/en/index.html

redacted is the wcd successor as far as I know, has a lot of what wcd had but not everything

@vaartis @alex @angristan I remember seeing this around before come to think of it, thanks for the reminder. I know a fair bit more about music encoding than I used to so interview shouldn't be too difficult now :)

@EmmaTheTrans the bittorrent client called bittorent is not open source

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!