Some bugs, comments and requests
Posted: Thu Nov 01, 2007 3:37 pm
Ill start with the bugs. The max connections per torrent option doesn't work.
I've set it to 40 to test it and after 2 minutes its already connected to over 100 peers per torrent.
The global setting seems to be working though, but it wont help if 2 torrents "steal" all connections and leave the other torrents with no room to connect. It also seems to have an impact on surfing alongside deluge.
Another thing I've noticed is that deluge can't seem to max out my download bandwidth.
I've set up 3 torrents. Each one of them should max out my connection, so all 3 combined should max out my connections too right? Wrong, it barely gets past half of my download bandwidth.
Another bug is that sometimes I have paused torrents in my list that have a status of 0%, while they are finished. So I have no way of seeing which torrents are queued and which are done and queued for seeding. Maybe adding a "stop" function for torrents and improving the status function would be better.
The stop function for torrents is actually a request of mine, as is the ability to set the maximum number of active downloading and active seeding torrents. I want to be able to keep the torrents i have downloaded for the following reason:
I download lots of small torrents, I usually just load them in the client and it downloads them. Once they are finished they are added to the seeding list. Both the downloading and seeding list abide by the maximum number of active downloading and seeding torrents rule. Now once I've seeded enough I can stop them and they are kept in the list. Why is that useful? Because when i add new torrents it'll notify me that the torrent is already in the list and i know I've already downloaded it.
I'm using deluge 0.5.6.2 on Ubuntu 7.10 32bit, but I've seen these bugs on 0.5.5 and there is no mention of them in the Changelog so i guess this also applies for 0.5.6.2
-bb10
I've set it to 40 to test it and after 2 minutes its already connected to over 100 peers per torrent.
The global setting seems to be working though, but it wont help if 2 torrents "steal" all connections and leave the other torrents with no room to connect. It also seems to have an impact on surfing alongside deluge.
Another thing I've noticed is that deluge can't seem to max out my download bandwidth.
I've set up 3 torrents. Each one of them should max out my connection, so all 3 combined should max out my connections too right? Wrong, it barely gets past half of my download bandwidth.
Another bug is that sometimes I have paused torrents in my list that have a status of 0%, while they are finished. So I have no way of seeing which torrents are queued and which are done and queued for seeding. Maybe adding a "stop" function for torrents and improving the status function would be better.
The stop function for torrents is actually a request of mine, as is the ability to set the maximum number of active downloading and active seeding torrents. I want to be able to keep the torrents i have downloaded for the following reason:
I download lots of small torrents, I usually just load them in the client and it downloads them. Once they are finished they are added to the seeding list. Both the downloading and seeding list abide by the maximum number of active downloading and seeding torrents rule. Now once I've seeded enough I can stop them and they are kept in the list. Why is that useful? Because when i add new torrents it'll notify me that the torrent is already in the list and i know I've already downloaded it.
I'm using deluge 0.5.6.2 on Ubuntu 7.10 32bit, but I've seen these bugs on 0.5.5 and there is no mention of them in the Changelog so i guess this also applies for 0.5.6.2
-bb10
