This forum has been archived. All content is frozen. Please use KDE Discuss instead.

2.1beta: Great job! +2 feature requests

Tags: None
(comma "," separated)
imported4-blujay
Registered Member
Posts
60
Karma
0
I just wanted to send some kudos to the devs. 2.1 looks like it will finally be the release that makes KTorrent a serious alternative to Azureus. 2.0.3 never got decent download speeds for me; it would show most peers as snubbed and choked, but as soon as I upgraded to 2.1beta, all that went away. Now, with a decent torrent with decent peers, KTorrent can consistently saturate my connection up to the max download speed limit. Awesome!

The only requests I have now are:

* A seeding priority system like Azureus has. It lets you seed the X files that need seeding the most, giving them decent bandwidth, instead of seeding everything at the same time, while giving decent bandwidth to none of them.
* A setting like Azureus's that automatically downloads X torrents until the bandwidth limit is reached. Meaning, if it was set to 2, then if the two highest-priority torrents can achieve the download rate limit, only download those two. But if they can't achieve the limit anymore, download more torrents simultaneously until the limit is reached. Then if the two top torrents can achieve the limit again, stop downloading other torrents. This way you get the files you want the most soonest, while not leaving bandwidth unused.
George
Moderator
Posts
5421
Karma
1
blujay wrote:* A seeding priority system like Azureus has. It lets you seed the X files that need seeding the most, giving them decent bandwidth, instead of seeding everything at the same time, while giving decent bandwidth to none of them.


You can use the queue manager to achieve this, you set some limits on the maximum number of torrents to seed and then you use the QM to give torrents priority. And if you set max share ratios, the QM will automatically switch to another one when the max share ratio is reached.

* A setting like Azureus's that automatically downloads X torrents until the bandwidth limit is reached. Meaning, if it was set to 2, then if the two highest-priority torrents can achieve the download rate limit, only download those two. But if they can't achieve the limit anymore, download more torrents simultaneously until the limit is reached. Then if the two top torrents can achieve the limit again, stop downloading other torrents. This way you get the files you want the most soonest, while not leaving bandwidth unused.


That could be an interesting feature.
imported4-Ivan
Registered Member
Posts
819
Karma
0
George wrote:
* A setting like Azureus's that automatically downloads X torrents until the bandwidth limit is reached. Meaning, if it was set to 2, then if the two highest-priority torrents can achieve the download rate limit, only download those two. But if they can't achieve the limit anymore, download more torrents simultaneously until the limit is reached. Then if the two top torrents can achieve the limit again, stop downloading other torrents. This way you get the files you want the most soonest, while not leaving bandwidth unused.


That could be an interesting feature.

Indeed. It could be somehow implemented in Queue Manager I think. I'll add it to my notes and see what I can do.
imported4-blujay
Registered Member
Posts
60
Karma
0
George wrote:
blujay wrote:* A seeding priority system like Azureus has. It lets you seed the X files that need seeding the most, giving them decent bandwidth, instead of seeding everything at the same time, while giving decent bandwidth to none of them.


You can use the queue manager to achieve this, you set some limits on the maximum number of torrents to seed and then you use the QM to give torrents priority. And if you set max share ratios, the QM will automatically switch to another one when the max share ratio is reached.


Well, almost, but that's not quite the same thing. Azureus calculates a seeder/leecher ratio for each torrent and gives each torrent a rating based on it. For example, a torrent with 1 seeder and 10 leechers would have higher seeding priority than a torrent with 5 seeders and 20 leechers. That's the basic idea, although from watching it, I think it also takes into account the absolute number of seeders; for example, a torrent with 1 seeder and 10 leechers seems to have higher priority than a torrent with 10 seeders and 100 leechers, even though the ratio is the same.

By the way, maybe you could add a global share limit ratio setting? =) It gets old having to set it for each torrent separately.

Keep up the great work!
stoeptegel
Registered Member
Posts
1075
Karma
0
blujay wrote:By the way, maybe you could add a global share limit ratio setting? =) It gets old having to set it for each torrent separately.


It's in the beta, so update ;)


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar