Start Deluge with 600+ torrents in it

[Simbiat]

Not to seem pushy or anything, but is there any ETA for release with faster work with a lot of big torrents and a working console? It's just that my project (a12.net.ru) is getting too great a load now (again), and I actually NEED to start using torrents (and thus a seedbox) to reduce the load (via partial decentralization) and continue providing the service with acceptable uptime...

[bro]

ETA for official release is unknown, but it will happen eventually. I can update the Windows test bundle with the console bug fixed if that helps?

[Simbiat]

ETA for official release is unknown, but it will happen eventually. I can update the Windows test bundle with the console bug fixed if that helps?

that would be great. besides that will allow volume testing for the client, which is also beneficial for you guys

[bro]

Updated with new 1.4 dev package and libtorrent 0.16.10: http://ge.tt/330gw2H1/v/0

Edit: link updated again

[Simbiat]

Gonna try now. Correct link is http://ge.tt/1qLizvE1/v/1?c though...

[Simbiat]

Seems to work. Although settings still do not pop-up for me. Time for stress testing now (=

[Simbiat]

"Start" button in top panel does not seem to work. Although, when I chose "resume all" through context menu for "Paused" torrents - they were resumed.
Also with almost 1900 torrents deluge.exe eats 3 Gbs of RAM and deluged.exe - ~1,2 Gb.

[bro]

Are you sure that is actual memory usage, and not virtual memory? With nearly 3000 torrents, my daemon uses 350-400MB and GTK client 100MB.

[Simbiat]

Are you sure that is actual memory usage, and not virtual memory? With nearly 3000 torrents, my daemon uses 350-400MB and GTK client 100MB.

yes, I am sure. my page file is barely touched and I have ~2 GBs of my RAM left... Out of 16.

It's possible, that there is a memory leak of some kind... I am waiting for it to check all those torrents. After it's done - I'll restart the client and see how much it consumes then.

[Simbiat]

Pity... seems like another show-stopper for me in terms of using Deluge as as a seedbox: my services is generally automated. So, I have a script, which creates torrents and adds them to deluge. But also require to check the status of those torrents and clear them up from Deluge and from database if required. When I'm checking the torrents, I planned to use "info" command to check if torrent exists in Deluge (and in correct status). I have 1850 torrents now and this command seems to simply hang... Or maybe it takes a lot of time for it to get all the information =( Since I need it to be run frequently this is a problem for me =( Or it will require extra manual work from me, which I'd prefer to avoid, if possible...

BTW, counter near "All" category shows 0... Always. In the 1.4 dev build, that is.