this post was submitted on 01 Oct 2024
193 points (99.5% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55056 readers
320 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -1 points 2 months ago* (last edited 2 months ago) (4 children)

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.

[–] [email protected] 25 points 2 months ago (1 children)

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.

[–] [email protected] 4 points 2 months ago

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.

[–] [email protected] 23 points 2 months ago* (last edited 2 months ago)

Just run 5 instances of transmission for your 5000 torrents!

Orrrr I could use a program like qBit or rTorrent that is designed properly.

[–] [email protected] 5 points 2 months ago

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

[–] [email protected] 2 points 2 months ago

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.