Deluge
Cant seed properly
-
TidusBlade
- Member
- Posts: 29
- Joined: Fri Sep 28, 2007 12:28 pm
- Location: Melon Island
Re: Cant seed properly
I'm having this problem with 5.5 so I'm guessing it's on all versions
Re: Cant seed properly
Am still having this problem with Deluge 5.6
torrents seed back Ok using Azureus :-/
torrents seed back Ok using Azureus :-/
-
F for Fragging
- Member
- Posts: 11
- Joined: Sun Jun 03, 2007 2:52 pm
Re: Cant seed properly
I noticed that the bug report concerning this bug, which was linked on the bottom of the first page of this topic, was closed. Markybob's reply seemed a bit strange, so I asked in IRC why the bug was closed:
<F_for_Fragging> http://dev.deluge-torrent.org/ticket/564 -> your reply seems a bit strange, I don't understand why you closed this bugreport markybob?
<F_for_Fragging> the bugreport links to a forum topic with replies from a lot of users, including me, experiencing this bug
<markybob> seeds are specifically targeted by isps. the difference is that in a seed, the bitfields are sent full, which is a big red flag to the isps. therefore seeds are *far* easily to limit than normal torrents. this should be fixed in svn by the use of lazy bitfields, but it's not a guarantee
<markybob> s/easily/easier
<markybob> so, use svn if you're having problems.
<F_for_Fragging> oh, so the bug actually was fixed? I'm sure that my ISP isn't out to limit Bittorrent traffic like other ISP's, and other Bittorrent clients - like µTorrent on Windows - work fine when seeding
<markybob> i dont doubt it. i have no idea what utorrent does (obviously since it's closed source), but i assume it tries to hack around it in much the same way that we do in svn with lazy bitfields
<F_for_Fragging> http://dev.deluge-torrent.org/ticket/564 -> your reply seems a bit strange, I don't understand why you closed this bugreport markybob?
<F_for_Fragging> the bugreport links to a forum topic with replies from a lot of users, including me, experiencing this bug
<markybob> seeds are specifically targeted by isps. the difference is that in a seed, the bitfields are sent full, which is a big red flag to the isps. therefore seeds are *far* easily to limit than normal torrents. this should be fixed in svn by the use of lazy bitfields, but it's not a guarantee
<markybob> s/easily/easier
<markybob> so, use svn if you're having problems.
<F_for_Fragging> oh, so the bug actually was fixed? I'm sure that my ISP isn't out to limit Bittorrent traffic like other ISP's, and other Bittorrent clients - like µTorrent on Windows - work fine when seeding
<markybob> i dont doubt it. i have no idea what utorrent does (obviously since it's closed source), but i assume it tries to hack around it in much the same way that we do in svn with lazy bitfields
-
alleyoopster
- New User
- Posts: 6
- Joined: Mon Oct 22, 2007 6:52 am
Re: Cant seed properly
Well the bug closure shows this as a reason.
What markybob said indicates that deluge is implementing lazy bitfields which will help the seeding. With this I can only assume that other torrent clients already have this implemented. If this is the case then it is good. Deluge devs are aware of the problem and it's being dealt with.
The reason stated for closure is not helpful to anyone and not helpful to deluge.
I have to admit I also find this a little strange. I tried to message markybob on IRC, but he did not respond. It is clear that learning how bittorrent works is not going to get deluge to work properly. I myself can use rtorrent, ktorrrent or any other without this problem with the same ISP, so fingers point at a problem in deluge.Change History
11/05/07 01:36:17 changed by markybob ¶
* status changed from new to closed.
* resolution set to invalid.
sigh. you need to learn how bittorrent works.
What markybob said indicates that deluge is implementing lazy bitfields which will help the seeding. With this I can only assume that other torrent clients already have this implemented. If this is the case then it is good. Deluge devs are aware of the problem and it's being dealt with.
The reason stated for closure is not helpful to anyone and not helpful to deluge.
Re: Cant seed properly
There's a good chance that markybob is a bit overworked and didn't learn about that libtorrent fix before sigh-ing and closing the bug 
.
.dev: webui, core, labels | irc:vonck7 |
-
alleyoopster
- New User
- Posts: 6
- Joined: Mon Oct 22, 2007 6:52 am
Re: Cant seed properly
Yeah, well maybe I was I bit harsh. I am happy that the devs are aware of the problem and we get another good bittorrent client in our arson.mvoncken wrote:There's a good chance that markybob is a bit overworked and didn't learn about that libtorrent fix before sigh-ing and closing the bug
Re: Cant seed properly
I noticed the problem too but I think there is a catch here. I'm seeding 41 torrents currently. The overall seeding speed is arround 100kbps. When I pause all torrents and activate the latest one (only one active) I reach speeds of 300-400 kbps. When I unpause all the torrents the speed drops down again (in a matter of seconds). Yesterday I couldn't download one torrent but when I paused the other torrents it started to download instantly (with a very good speed).
I think there are some problems with managing multiple torrents. I'm using version 0.5.5 (manual build) on Fedora Core 6.
edit:: I did a little more testing. Pausing a single torrent and unpauseing it back boosts the speed up for a while. I don't know if this is normal behavior but the difference in the speed is ... 10+ times. I'm not sure what formulas are used to determin who will seed to whom and whatsoever, but the fact is that 'restarting' the torrent/shutting all other torrents down changes the speed... I used bit torrent up to day and it doesn't seem to have these problems (It has other problems however
thats why I decided to change). It's written in python ... probably the author of deluge can check (I know that this is very hard) how the seeding is organized there but there is certainly something wrong with it.
I think there are some problems with managing multiple torrents. I'm using version 0.5.5 (manual build) on Fedora Core 6.
edit:: I did a little more testing. Pausing a single torrent and unpauseing it back boosts the speed up for a while. I don't know if this is normal behavior but the difference in the speed is ... 10+ times. I'm not sure what formulas are used to determin who will seed to whom and whatsoever, but the fact is that 'restarting' the torrent/shutting all other torrents down changes the speed... I used bit torrent up to day and it doesn't seem to have these problems (It has other problems however
thats why I decided to change). It's written in python ... probably the author of deluge can check (I know that this is very hard) how the seeding is organized there but there is certainly something wrong with it.Re: Cant seed properly
Just posting to say that I have the same problem.
While downloading (leaching) a torrent, the upload speed for that torrent is as it should be (good).
When download is completed, so the torrent is only being seeded, the upload speed is for the most part zero.
A big problem with private trackers.
Deluge 0.5.6.2
WinXP
While downloading (leaching) a torrent, the upload speed for that torrent is as it should be (good).
When download is completed, so the torrent is only being seeded, the upload speed is for the most part zero.
A big problem with private trackers.
Deluge 0.5.6.2
WinXP
Re: Cant seed properly
Just tried with Ubuntu 7.10 the Gutsy Gibbon.
Same problem, when download is finished, there's no seeding on my end.
Same problem, when download is finished, there's no seeding on my end.
Re: Cant seed properly
Hello,
I had the same problem. After days of moaning and groaning, I went to "preferences > bandwidth > maximum upload slots" and increased it by 5.
It instantly started seeding the peers from my completed download. I wasn't connected to a tracker at the time as far as I could tell. I had either a timed out or connection refused alert. But it didn't seem to matter.
Clifton
using 0.5.5 0n Gutsy
I had the same problem. After days of moaning and groaning, I went to "preferences > bandwidth > maximum upload slots" and increased it by 5.
It instantly started seeding the peers from my completed download. I wasn't connected to a tracker at the time as far as I could tell. I had either a timed out or connection refused alert. But it didn't seem to matter.
Clifton
using 0.5.5 0n Gutsy