Is there any downside to leaving something seeding indefinitely? Typically I just leave all my torrents seeding whenever I’m done 24/7 (whenever the VPN is on) but is there any detrimental issues to seeding too much?
It doesn’t bother me I was just curious if there was ever a such thing as too much seeding since I have like 20+ things seeding and maybe one thing downloading.
Speed isn’t an issue since I have gigabit internet.
No issues at all! Obviously speed caps will be useful since eventually you’ll have enough torrents that even gigabit will be saturated, but even a low speed can mean a lot over a long time.
Question for the group:
Using Unraid can I pull from sonarr and then add to Jellyfin (watch it) and also seed? That would be amazing. Usually I have my deluge stop seeding so I can move the file to my data folder and not have duplicate files
On mobile but look up TRASH guides. That’s what I used in my setup and I’m able to watch stuff almost as soon as it downloads and I still let it seed for awhile after. Also using Unraid, Arr apps, and Jellyfin.
I use qbittorrent so maybe this is why, but when my downloads finish theyre moved to my movies/tv folder but since qbittorrent handles that, it keeps seeding the files afterwards.
I download to a 1TB USB drive. ARR’s then copy the completed files to the NAS proper. When the USB fills I clear up ~100GB of the oldest files. Then the cycle continues.
I don’t know if it’s good or not but I just created a library in Jellyfin pointing to my Media folder that I download torrents to. It’s probably not the same as what you’re doing since it’s my regular desktop but it works for me.
My next goal is to get an actual home server so I can let my parents view my jellyfin too.
No with a VPN you are good. Sharing is caring.
Bless you.
I deliberately leave stuff that’s been a bastard to get seeding as long as physically possible. We’ve all felt the pain. Don’t spread it.
Exactly. There’s little point in keep seeding popular torrents on public trackers (it’s a different story for private trackers though).
But if you have a rare torrent that has been difficult to complete, please please keep seeding it for as much as possible!
Seeding some torrents since 2022. So no.
Only for your bandwidth though. Make sure to set bandwidth caps for either trackers or timeslots (e.g. evening for gaming time)I seed content I get as much as I can to I2P. No data caps here so not really any downside. You do have to limit stuff a bit to not overwhelm your connection at some point
does your ISP cap your data like 1TB per month? If you reach the 1TB, your speed will slow down.
I’m seeding around 1600 things. I tried to seed a news paper I need, around 5k items and it crashed qbit.
Depends on how many torrents you have. You have a set number of global peers. So if all of those peer slots are occupied by leechers, then you won’t have any room to download anything. A way around this is torrent priorities.
Setting seeding torrents to low priority will ensure that any new torrents imported at normal priority will download without an issue. You can even set seeding torrents to high priority to ensure that they’ll always seed, even if it means taking priority over your downloads.
Ooh I never thought to use the priority more! I’m doing that today!
You have a set number of global peers
You do know that you can increase this, right?
You also know that if it’s set to high, it will overload the switch? Increasing it without thinking isn’t smart.
You need to have an appropriately set number of global peers. You can’t just “HAHA NUMBER UP!” just for the hell of it…
You can if you don’t run anemic networking gear. Have three PCs running torrent apps, with a total number of allowed connections sitting at right around 1200 between all of the torrent clients. Zero issues.
You’re not having issues because it’s very likely it’s limited by your ISP regardless. There’s simply no way a consumer ISP (or VPN) is allowing 1200 simultaneous UDP connections. So you could likely set it to a million and have no issues. Because you’re being limited to ~250-500 at the protocol level by your ISP/VPN. lol
Situations like this, torrent priority is even more important because there’s a high likelihood you’re not able to connect to peers you otherwise would be able to if you were using priorities…
I generally keep things seeding indefinitely when I keep the content, to make the network stronger. For other things I delete it once it surpasses at least 1.0 ratio.
The only real downside to seeding indefinitely is that you have to store it, but I would be storing what I do that for anyway.
Seeding is the true fuck you to the the media corpos.
Get fucked parasites.
In the case of Transmission, I’ve noticed that depending on server resources, there’s an upper limit to how many seeds you can run and still get reasonable downloads. No idea why, but if you seed like 100-ish items, you basically never get decent downloads, and it’s not like the upload speeds are great either, so it’s not bandwidth.
I think it’s related to the number of open connections. If you have 100+ torrents you’re going to have a lot of open connections to leeches, so your new downloads will have to wait for slots to open.
You could fix it by setting all of your seeding torrents as low priority, so your new normal-priority downloads will start.
There’s no such thing as too much seeding.
Well, maybe the 85tb of Ubuntu 24.04 I’ve done is too much, but I mean, whatever.
(I’ve got basically everything I’ve downloaded in the last 7 years seeding, some 6000 torrents. qBittorrent isn’t the most happy with this, but it’s still working, if using a shit-ton of RAM at this point.)
You’re a hero.
This is especially useful for Books. Small torrents are so hard to find. I perma seed books/audiobooks and copy to my slskd directory because they’re so hard.
I have this book. It’s a few Kb in size and I have already seed Gb of it. It has an insane ratio. I think I will never delete that torrent.
Doing the lords work.
Is there an easy way to permaseed in qBittorent?
Permaseed is the default. To disable perma-seed would be to set an upload limit, like a time amount or a ratio.
I run a ratio of 2:1 for most stuff
If your router is the one that your ISP provided, torrenting can affect your internet connection stability by having too many connections active, because most of the time that hardware is trash (at least from my experience).
Most (all?) torrent clients support limiting the number of active connections. This should prevent your router from being overloaded.
In my experience 500 shouldn’t be a problem. On that note, limiting upload bandwidth to something less than the available upload bandwidth is important too.
250 active connections is the limit with my ISP provided router. You can get beyond that, but it causes a lot of instability, and eventually, the network fails and the router reboots.
On another note, I don’t limit my bandwidth at all and I’ve managed to get uploads/downloads of up to 142% the speed which I should get.
250 active connections is the limit with my ISP provided router
So buy your own.
250 connections really is not much. I ran a matrix server for a while and joining a few large rooms (1k+ servers) made the connections reach a few thousand – which made the router slow down/unstable/reboot.
I’ve noticed the same for my upload bandwitdh, with it being 170%-200% of its advertised maximum speed. Sadly the same can’t be said about the download bandwidth. Luckily fiber will be available in a few months.
Hm, interesting. I didn’t bother with a personal router for the longest time (aside from an old Linksys I got because it works with ExpressVPN) because I have fibre optic but I might go out and look for one now.
One related thing to watch out for is the state table size - one of my old cheap routers back in the day showed how full it was and it was hitting 100% a lot and seemed to grind the network to a halt when it did (I was in a house of 5 young people with lots of devices and multiple people torrenting behind a cheapo Netgear running ddwrt). That’s what lead me to switch to high end or x86 based routers. Being able to see the state table stats really helps to know how likely it is to be a problem, it’s so big when using opnsense on an x86 box that I don’t think it ever goes above 1% now.