I’m migrating because Transmission is horrible for a large amount of torrents (multiple of hundreds) due to the complete lack of concurrency capability. But I’ll miss Transmission. This configuration has spanned many different operating systems and was migrated from transmission-gtk to transmission-daemon.
Translation of all the numbers:
Downloaded bytes: 64.4TB, 58.6 TiB
files added: 26.8 million.
seconds active: 3.84 years
session count: 802 times started
uploaded bytes: 909 TB, 827 TiB
ISP is like
THX for contributing
Thank you for your service o7
NP. I’m gonna get way faster upload with qB, so yay. I used to do like a TB a day but Transmission has been sluggish lately. I’ve been limited to maybe a quarter.
I was just gonna ask why the switch but I see now. That’s wack hope transmission can be just as good one day
It’ll be easier to just fork QB at this point. Even features like “this torrent already exists in your list, would you like to merge trackers” are completely nonexistent in Transmission.
Mind if I ask which VPN service you use?
Mullvad of course but they turned off port forwarding :(
Air is good. Fixed port too so that’s not something you have to deal with more than once.
I gotta get my ship sea worthy again.
Thiiiiink it goes something like this:
- Catch a VPN - heard good about Mulvad but no port forwarding? Any other recs?
- Set that up - maybe need more info here 😅
- Use torrent client/website?? - what are the cool kids doing these days, qbittorrent?
Feel free to shoot DMs too 🤙 I just love sailing advice.
i2p?
Mullvad, Proton and Surfshark are good. Proton has port forwarding if you need it.
Look up how to bind a VPN to your torrent client and you’ll be good.
qBittorrent is the best by far
qbittorrent-nox is my go-to. No need for a desktop UI, just give me the web-ui. That’s all I use anyway, and I can manage it from my phone wherever I am.
I can answer 1 and 3 easily. AirVPN is decent and Qbit seems to be the consensus.
Qbittorrent, plex or jellyfin and if you’re into it, the arr suite for automation, all configured in a single docker compose file. It’s beautiful. But I don’t know if it’s as nice under Windows (if that’s what you’re using). For Linux it’s definitely super nice
If you’re dockerizing it, you’re dockerizing it under Linux. Nobody dockerizes anything under Windows, that’s the definition of insanity. And the tool itself works basically the same whether you’re using Windows or Linux.
Thank you, kind sir o7
wow. i feel shamefull and opening qbittorrent right now :D
o7
That’s only about 7 MB/s, that’s not that much!
That’s over half a 100mbit line 24/7.
I have my upload capped at 6MiB/s since that’s ~half my 100mbit upload. (I can’t get symmetric gigabit internet here, at least not until fibre-to-the-door lines are run in the next couple of years.)
Impressive numbers for home internet.
That’s only ~5% of a gigabit line.
Bet
Need to do the same but from deluge
I’m migrating because Transmission is horrible for a large amount of torrents (multiple of hundreds)
That doesn’t sound like too many, you’re saying you’re at under 1000 torrents? How many multiples of hundreds are we talking?
Surprised Transmission has issues seeding that many, thought Transmission 4.x made improvements in that area. How much RAM does your system have? Maybe at some point you just need more system resources to handle the load.
PS - For what it’s worth you can still stick with Transmission and/or other torrent clients & just spread the torrents among multiple torrent client instances. e.g. run multiple Transmission instances with each seeding 1000 or whatever amount of torrents works for you.
I don’t know what the issue is. I genuinely think it’s because Transmission is entirely single threaded. Memory is fine, running at 50% utilized.
And it’s like 3-4 hundred ish.
just spread the torrents among multiple torrent client instances
No. Just… no.
And it’s like 3-4 hundred ish.
That should be easy for just about any torrent client (including Transmission), could be worth opening an issue at their GitHub page https://github.com/transmission/transmission/issues
Hopefully switching torrent clients resolves that for you.
Just run 5 instances of transmission for your 5000 torrents!
Orrrr I could use a program like qBit or rTorrent that is designed properly.
It shouldn’t be too many, my hardware wouldn’t have been considered high-end ten years ago but transmission is handling thousands just fine for me. It takes a lot longer to start up with this many, probably 20-30 seconds, but runs without issue after that.
Surprised Transmission has issues seeding that many, thought Transmission 4.x made improvements in that area. How much RAM does your system have? Maybe at some point you just need more system resources to handle the load.
PS - For what it’s worth you can still stick with Transmission and/or other torrent clients & just spread the torrents among multiple torrent client instances. e.g. run multiple Transmission instances with each seeding 1000 or whatever amount of torrents works for you.
Those are duck tape solutions. Why use them when there is a good solution
