Deluge Forum

I am a recent Ubuntu Jaunty Jackalope upgrader who picked up 1.1.6 with that upgrade, as so many of us did. From other forum posts, it would seem that I am fortunate, since 1.1.6 worked straightaway, losing only my ratio data.

But there is one change from the 5.5.x version I had with Intrepid Ibex. It may be possible to configure 1.1.6 to work similarly, but I haven't been able to sort it out. I hope one of you can help.

It seems that seed and download queues interact in 1.1.6, and that downloads take priority - that is to say that if I have 20 total slots (10 download and 10 seed) that a new download can make a seeding torrent go to queued status. A similar configuration in 5.5.x would continue seeding a given torrent(s) until the ratio was reached, keeping new torrents in queue until seeding was finished.

I much prefer the old behaviour, as many of my trackers are ratio monitors and my upload speed is poor. The current 1.1.6 configuration has the net effect of placing me in ratio debt at a rate I will never be able to repay.

Any help appreciated. I've exhausted my ability to frame search terms; please reply if only to let me know that my question is unclear.

If you want it to finish seeding before it downloads any new torrents set your total upload and total active to same value, ie. set both to 10 and set total downloading to like 2 or something.

Thanks for the tip, Loki. While it does improve my situation, it isn't the behaviour I'm looking for.

What I want is the behaviour from 5.5.x - I want a given torrent to hold it's active place from the time it starts downloading until it stops seeding. I don't want other seeding torrents or other downloading torrents to take priority and enqueue their predecessors - I want a FIFO order.

My reason is that activity on my typical torrents tends to peak soon after their initial availability. I therefore occupy the shortest total window by both downloading and seeding when the torrent is most active, which I manage by the order in which I add them.

Is that clearer? Should I repost with a different topic?

Thanks-
psantucc

psantucc wrote:Thanks for the tip, Loki. While it does improve my situation, it isn't the behaviour I'm looking for.

What I want is the behaviour from 5.5.x - I want a given torrent to hold it's active place from the time it starts downloading until it stops seeding. I don't want other seeding torrents or other downloading torrents to take priority and enqueue their predecessors - I want a FIFO order.

My reason is that activity on my typical torrents tends to peak soon after their initial availability. I therefore occupy the shortest total window by both downloading and seeding when the torrent is most active, which I manage by the order in which I add them.

I have never used pre-1.0 versions of deluge, so I cannot speak about the differences to the current version, but I would say that I'm getting the behavior you describe on 1.1.7. My queue settings are: total active = 30, total active downloading = 5, total active seeding = 25. I have a fairly fast internet connection (20/2 ADSL) and deluged is running on my Linux home server, which is why I have values above the recommended default one.

Sadly still not what I'm hoping for. I seem to be describing it poorly; perhaps this:

Consider this situation - I set up with

2 max downloads
10 max seeds
10 max total.

I download 10 torrents, and all 10 start seeding.

I then add an 11th torrent.

Under 1.1.6, the new torrent starts downloading and one of the seeding torrents becomes enqueued.

What I want is for the 11th torrent to start and stay enqueued until one of the seeding torrents finishes.