Deluge Forum

f.lambe wrote:ok, i'll do that. It's necessary to use thin client with deluged daemon?

I'm not sure, I tested this only with the daemon. Anyways, it's easier to just profile the component that behaves oddly.

Smyl3 wrote:

bro wrote:Can verify if it's the daemon or client that uses all the CPU?

Can I? I'm using the windows version of Deluge..

Did you check the link to thin client setup?

bro wrote:Did you check the link to thin client setup?

On page 1? Yes, I realised there is a thin client in the windows installation already as well. I ran the deluged.exe and I could connect to it with the deluge.exe:
deluged.exe used 0-1% cpu power
deluge.exe used 1-3% cpu power (it regularly did <21% spikes, sometimes that occured as well when I started to move its window)
Almost got same values with a seeded torrent (no seeding activity tho), and without any torrent. (state dir files deleted)
When I switched back to classic mode, deluge.exe began to use 10% cpu power again as before, without any torrent.

@Smyl3
Created ticket for this issue: http://dev.deluge-torrent.org/ticket/2330

@Smyl3
We think this is caused by using the twisted gtk2reactor to handle all the events. On Windows, the reactor uses select which has trouble handling the events for both the daemon and the client. A solution is to simply use thint client mode, and just make it automatically connect to the localhost on startup.