Hi, the subject pretty much says it all. It would be nice if only the number of torrents being actively uploaded at any given time counted towards the Max seeds limit, not including the number of torrents awaiting for someone to download them.

rihad wrote:Hi, the subject pretty much says it all. It would be nice if only the number of torrents being actively uploaded at any given time counted towards the Max seeds limit, not including the number of torrents awaiting for someone to download them.

Why not just use the feature to decrease the priority of torrents if they become inactive for too long ?

George wrote:Why not just use the feature to decrease the priority of torrents if they become inactive for too long ?

You mean the "Decrease priority of torrents which are stalled for too long" checkbox? I never thought of it, thanks.
But still I'd like to lower the load on the computer. 10-20 simultaneous seeds (multiplied by several upload channels per torrent) is hardly something an average desktop HDD is designed to do. So I'd like to limit that to 5 torrents, BUT setting max seeds to 5 having 50 torrents on the upload queue might not be optimal, because only 5 out of 50 would be allowed to the outside world, the rest would be put on hold. See what I mean?

I fail to see the difference, between running 5 torrents, and running 20 torrents and only allowing uploads on 5 of them.

Let me put it this way: 5 torrents out of 20 are more likely to be actively uploaded at any given time than 5 torrents out of 5. Frankly, the checkbox you mentioned goes a long way toward doing almost the same thing by mangling the priorities, although it is prone to time lags.