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
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.
Orrrr I could use a program like qBit or rTorrent that is designed properly.
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.
No. Just… no.
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.