Deluge Forum

Hey,

I've moved to Deluge from uTorrent due to ads and nonsense. been using Deluge for a few months now, but it's never worked well, unfortunately.

I've got terrible client lag. If I click it, several seconds can pass before it reacts. It goes grey and the cursor becomes the windows 7 "loading circle".

This happens even with just one single torrent running, with very slow download, even single digit kB/s speeds.

Then sometimes it runs without this lag...

I'm running
Windows 7 64-bit
Intel Core i5 2500K
8 GB DDR3 RAM

Downloading to a Western Digital 1.5TB drive which is otherwise behaving well and is not in sleep mode or anything.

PS: Also annoying is that Deluge will not allow me to change away from these annoying Norwegian menus. I want them in English!

HI

Have you tried running in daemon/thin client mode?

Ok I just tried that. Now the client is consistently responsive to clicks, but..

I loaded a torrent, just a sample torrent, thousands of seeds, and when I choose to stop it, or even to delete it with data, it can take like 5-6 seconds to respond. The click is registered immediately, but the action is delayed...

I guess it's better than before, but still a weird bug.

Hi - I am also having this problem, it's really bad for me actually. Any download torrent brings the thin client to its knees, just not a reliable means of interfacing. It's smooth as silk with no active downloads.

I've ditched the thin client for now and just rsync the files to a pickup/watch folder while I SSH the deluge-console to confirm they were picked up. I'll open the client to get a quick view, but I know better to mess with it if they're still downloading - I only use it to check that I'm seeding if I dont feel like using SSH, super sad about that

Please help or advise, much appreciated.

Running in Thin Client mode:
Deluge 1.3.11
OSX 10.9.5 as Client
Raspberry Pi 2 B as Server
Native SD card or external hdd/sdd as storage, acts the same in any storage config

Thanks!

edit: To clarify, I've had the most issue when adding torrents through the client interface - it freezes the whole thing. Adding any additional is a wait and see kind of ordeal. The interface refreshes every 15-20 sec, only updating a few times a minute while completely frozen between updates.

That sounds different to OP issue and it's likely RPi limited resources coming into play. Have you checked resource usage on RPi when you see lagging? Also how many torrents?

It very well could be, but it seems deluged daemon runs fine (except once or twice randomly). The files finish faster than the initial eta and continue to be written while the client is frozen, performs better than i could ask when interfaced with deluge-console and a watch folder.

I am seeding anywhere between 30-100, but regardless if i download one or ten, it freezes the same. I have my config set as OP does now, thin client/server daemon. I'm experiencing the same issue OP noted after switching to the thin client, reactive buttons but extreme lag in response to user input and dl/ul status.

DrOnline wrote:The click is registered immediately, but the action is delayed...

I guess it's better than before, but still a weird bug.

Same here useing Deluge 1.3.12 on Qnap NAS with thinclient Deluge 1.3.12 on windows 10 x64.

Example of issue:
When starting the Deluge client and click connect to server the the CPU is useing 12% CPU on a Core i7 (8 threads) for 9 minutes and 37 sec before the connection shows info and torrents from the server.
Nas server have 11.1-30'% CPU usage and then stabilize around 33% when connected.

Aswell when closeing the client in windows it takes several minutes for the client to accept the command and it closes after 10-15 min maybe, same when clicking add torrent.

The commands in the client is registred but with a huge delay of the action.. its not a static value. 1/10 times it´s faster.
Useing 925 torrents right now, im going to decrease the number of torrents since deluge have problems when useing close to 1000 torrents. i will try disable watchtorrent dir aswell and see if it helps.

The NAS is on 24/7.