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.
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.)
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.
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.
Not really, at least not because of the data access. Drives mainly die because of their age.
SSDs will basically not degrade by reading them, they only degrade when you write to them.
HDDs can get degraded because of data access, but most HDD deaths are caused by bearing failures or head crashes, which are more of a matter of power-on hours.
What all of this means is that if you already kept your device on 24/7, your drives aren’t gonna degrade noticeably faster by having your torrent client accessing them all the time.
I have around 400 items seeding 24/7. No problems at all, except that I am sending from my media server via my desktop,so I need to set speed limits in my torrent client to keep from saturating the wifi connection. (Slowly working to get things migrated over…)
Not really, as long as your VPN setup is solid (assuming you need it to avoid letters) and you don’t mind the bandwidth usage. I have some ratios in the 500s
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.
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.
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 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.
Yeah I know I should, and it’s on my list, but I haven’t changed it yet lol. I’m making it work like this and if I can stretch it until they replace it for a more capable model, that’s money that I don’t have to spend on it.
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.
Edit: now that I think about it, if your VPN is working I wouldn’t expect any states related to peer connections to show up since your router won’t be NATing them, I guess I was just bold back in the day because it was a huge problem then.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.
deleted by creator
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!
No with a VPN you are good. Sharing is caring.
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.
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
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.
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.
Lots of permaseeders out there, you can be one too :)
There’s no real downside as long as your ISP doesn’t limit your bandwidth.
There’s wear and tear on your drives and your bandwidth usage, but if you meant from the tracker’s perspective - none, in fact the more the better
Is the wear and tear a considerable amount over time? Or just something to consider as it does some compared to not seeding 24/7?
Not really, at least not because of the data access. Drives mainly die because of their age.
SSDs will basically not degrade by reading them, they only degrade when you write to them.
HDDs can get degraded because of data access, but most HDD deaths are caused by bearing failures or head crashes, which are more of a matter of power-on hours.
What all of this means is that if you already kept your device on 24/7, your drives aren’t gonna degrade noticeably faster by having your torrent client accessing them all the time.
Drive failures have almost nothing to do with access if they are mechanical. Most failures are from bearing or solder interconnect failures over time.
Also, most seeding is in smaller chunks that are read and cached if popular… Meaning less drive hits than 1-1 read vs upload.
You will almost always have drives fail from other aspects like heat or power or old age before wear from seeding would ever be enough to matter.
I have drives in the excess of 10+ years, with several seeds that have been active for many years of those, that are still running just fine.
Seeding is the true fuck you to the the media corpos.
Get fucked parasites.
I have around 400 items seeding 24/7. No problems at all, except that I am sending from my media server via my desktop,so I need to set speed limits in my torrent client to keep from saturating the wifi connection. (Slowly working to get things migrated over…)
Not really, as long as your VPN setup is solid (assuming you need it to avoid letters) and you don’t mind the bandwidth usage. I have some ratios in the 500s
This guy Seeds
o7
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 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.
I’m seeding around 1600 things. I tried to seed a news paper I need, around 5k items and it crashed qbit.
does your ISP cap your data like 1TB per month? If you reach the 1TB, your speed will slow down.
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 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.
So buy your own.
Yeah I know I should, and it’s on my list, but I haven’t changed it yet lol. I’m making it work like this and if I can stretch it until they replace it for a more capable model, that’s money that I don’t have to spend on it.
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.
Edit: now that I think about it, if your VPN is working I wouldn’t expect any states related to peer connections to show up since your router won’t be NATing them, I guess I was just bold back in the day because it was a huge problem then.