Start Deluge with 600+ torrents in it

[Cas]

There are major improvements in development to deal with large number of torrents. Do your torrents have large numbers of files in them as that can cripple Deluge?

[Simbiat]

There are major improvements in development to deal with large number of torrents. Do your torrents have large numbers of files in them as that can cripple Deluge?

yes, they do. some of them have a lot of files. I mean like a LOT. should I try compiling 1.3.7 then?..

[laharah]

BTW, total size of the .torrent files themselves (632 of them) is 150 Mbs.

150 MB!? I think that might be part of the problem. That seems like it's way too high. My entire "state" folder containing all 582 of my .torrent files and my resume files only takes up ~20MB

[Simbiat]

150 MB!? I think that might be part of the problem. That seems like it's way too high. My entire "state" folder containing all 582 of my .torrent files and my resume files only takes up ~20MB

it simply means, those torrents contain data about a small number of files. the more files a torrent has - the bigger it is.

[laharah]

150 MB!? I think that might be part of the problem. That seems like it's way too high. My entire "state" folder containing all 582 of my .torrent files and my resume files only takes up ~20MB

it simply means, those torrents contain data about a small number of files. the more files a torrent has - the bigger it is.

I know, what I meant is that while you've only got 600 torrents, deluge is tracking milions of files that it has to hash out. Which would explain the startup times and your footprint.

[Simbiat]

I know, what I meant is that while you've only got 600 torrents, deluge is tracking milions of files that it has to hash out. Which would explain the startup times and your footprint.

well... uTorrent can handle 1300+ of such torrents with ease. Only if it would not go crashing randomly... And yes, it does not load them instantly, but it takes it up to 5 minutes. So, I guess, there is some logic, that slows the process down in Deluge.

[Simbiat]

So... 631 torrents were added. Client was closed and service stopped. Client was restarted. It was hanging for over an hour, until I killed it. Log attached.

I wonder what is it receiving, if it says this:

[DEBUG ] 19:19:01 gtkui:302 sent: 146.0 KiB recv: 5.4 GiB
[DEBUG ] 19:19:01 gtkui:310 sent rate: 0.0 KiB/s recv rate: 1.1 MiB/s

And all torrents were stopped...

I will also start it overnight and first half of the day, just to see if it loads at all. That is it will be hanging for at least 16 hours.

[Cas]

Are you using Deluge in thinclient mode?

[Simbiat]

Are you using Deluge in thinclient mode?

yes.

I launched it in debug around 22:15 (local time) and woke up just now (around 5:00) and.. It's loaded. Although by the log it's unclear WHEN it was loaded.

[Simbiat]

So... Before going to work I set all those torrents to check. Some of them failed, because contents in folders were updated, so it's ok. Most of them did get moved to "Seeding" status. And for some reason deluged.exe was using 25% of CPU and logs tell me, that I even sent out something and was still receiving something...