Hi all,

I started using the queue in my deluge install with the automatic rotation, as seeding 1000+ torrents simultaneously was causing performance and network issues. My downloads and uploads are a lot more active now, but the big issue I’m encountering is I will accrue HnRs on certain trackers when a torrent it rotated out of seeding.

Is there a way to force new torrents to stay actively seeding for X period of time? Even better, a way to force it only on specific torrents?

I do have an idea in mind of how to accomplish this:

  • Set up a watch dir for torrents that need to seed for lets say, 2 weeks minimum

  • Have that watch dir add torrents with auto manage turned off and add a specific “force seed” tag or something to identify them.

  • Create a script that will query deluge for the force seeded torrents, and if they have been added more than two weeks ago, turn auto manage back on and remove the force seed tag

  • Run that script on a cronjob every night

I believe the above should work, but it does seem overly complex. Any ideas?

  • Brickfrog@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Does seem a bit complex… are you sure you need to do all that? My own torrent clients (including Deluge) seem to work fine with queuing disabled and everything set to unlimited except for global connections maximum. In other words configure your global connections to whatever number works for you and your network & let the torrent client automatically manage everything else. You can also configure the Download/Upload maximum speed if you find your Deluge is maxing out your network bandwidth (and/or enable the Scheduler to do the same thing per day/hour).

    Another alternative - if you think the issue is the amount of torrents - you could try running multiple Deluge instances / multiple torrent clients & spread the load that way. Definitely doable with Deluge, you essentially run multiple deluged processes each pointing to their own settings folder & then connect to any of the running deluged processes via the Deluge thin client. Take a look at https://dev.deluge-torrent.org/wiki/UserGuide/ThinClient or search around for more info on that.

  • grehund@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    If you use the Label plug-in, you can edit the label options to set queue settings and to auto-apply that label to specific trackers. The queue settings are ratio, not time tho.

  • ram@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Ya, your problem is exactly why I switched from deluge. It’s just terrible at running more than a few hundred seeding torrents simultaneously. ^^;

    • mike901@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      What did you switch to? I’ve tried to give rtorrent a go, but config is a pain and rutorrent craps itself when you have a lot of torrents. rtorrent + flood is the most promising I’ve tried other than the obnoxious setup but I’m pretty entrenched in deluge and flood was pretty early in development when I tried.

      • ram@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        After fuddling around with other clients I eventually ended up back at qBittorrent.