#2384: invisible throttling bug?
--------------------------------------+--------------------
 Reporter:  demian                    |      Owner:
     Type:  bug                       |     Status:  new
 Priority:  major                     |  Milestone:  Future
Component:  Core                      |    Version:  1.3.6
 Keywords:  download speed throttled  |
--------------------------------------+--------------------
 hey,

 versions:

 deluged 1.3.6
 libtorrent-rasterbar 0.16.12 (same with 0.16.10)

 My deluge is behaving rather odd and because it's not that easy to explain
 i will add two gifs at the end of the post.

 So: I have 100Mbit downstream, meaning i should get up to ~11 MBps
 download speed. And with other torrent clients like Vuze or rtorrent i get
 that, if there are enough seeds, that is.

 But with deluge i never get more than 2 MBps downstream, irregardless of
 how many torrents i have open. As if i had throttled the dl speed.
 Upstream is NOT affected.

 So, i usually hang somewhere between 1.5 MBps and 2 MBps. On a single
 torrent I can get up to 4-5 MBps but it is very rare. I've actually only
 ever seen it on one torrent, which incidentally is also the only torrent,
 I can get the full 11 MBps, which i get by pausing and then unpausing...
 Yes, it sounds weird, there is a demo gif attached (gif 1).
 All other torrents I have tested so far cap at around 2 MBps and those are
 torrents which, if opened in rtorrent or vuze, download at least 3 times
 as fast, often at the cap of ~11 MBps.

 I have tried the unpausing with different torrents but this archlinux one,
 is the only one that resumes with full speed (gif 1).
 And to add to the confusion, if i have other torrents open while doing the
 pause/resume voodoo, global download speed will still be capped at 2 MBps.

 I have tried:
 current git version of deluge
 downgrading libtorrent-rasterbar (to 0.16.10)
 deleting all configuration files
 changing all kinds of options (DHT, Peer Exchange, TOS, Encryption, every
 bandwidth option to -1 etcpp)

 To me it seems, the problem has to be within the deluge code unless i am
 somehow missing a crucial option.

 Maybe someone here can make sense of this.
 Gifs:
 http://a.pomf.se/l84ay.gif
 http://a.pomf.se/v67dw.gif

 A log of the first gif (full speed after resume):
 http://bpaste.net/show/156682/

-- 
Ticket URL: <http://dev.deluge-torrent.org/ticket/2384>
Deluge <http://deluge-torrent.org/>
Deluge project

-- 
You received this message because you are subscribed to the Google Groups 
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to