Web UI - High CPU usage

[davewantsmoore]

Hello. I like Deluge.

When running the daemon and webui (on Ubuntu 9.10)... I get very high CPU usage from the client displaying the webui.
This only happens with a large amount of torrents (I only have a few running, but I have a lot paused).

The high CPU usage happens from all operating systems (Linux, Windows and Mac), and browsers.
I will often get "connection to server lost"

[z0id]

+1

I have almost 200 torrents and the WebUI is unusable. CPU is at 100% and firefox says the /js/ext-base.js and /js/ext-all.js scripts are unresponsive. However, if I select a category (e.g. Downloading torrents) which displays only a few torrents in the main list, the interface returns to normal. Rarely, the GTK interface loads the cpu at 100%, too; haven't figured out what causes it yet.

[scarybiscuits666]

Same problem here using version 1.2.0-2. With top reporting 101% and higher CPU usage on client (Ubuntu 9.10 desktop), connecting to Deluge Web UI 1.2.0. I have tested this with Firefox 3.5.7 and Google Chrome 5.0 in Ubuntu and also Windows XP SP3 - same issue issues.

Total of 76 torrents in queue but not all active - browsers become completely unstable, as described above. And also getting this error message in firefox:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: https://[server]:[port]/js/ext-base.js:159

If there is anything I can submit to get this classified as a bug then please let me know - need to get this sorted soon as its useless at the moment and very unstable. Thanks.

[scarybiscuits666]

I have just seen that there is a ticket open with a similiar issue - though no indication of a resolution as of yet.

However 3 hours ago a change was made here to the guide, it relates to changing the init.d script to fix a karmic problem with the webui daemon - is there any way to confirm exactly what this does and if it relates to this high CPU issue?

[johnnyg]

The change made to the init script just reverts to calling the web ui in the 1.1.x compatible way, it has no affect on performance.

That said, there have been major performance improvements going on in trunk (which will be 1.3) relating to the web ui.

[mel]

Had the same issue and had to revert to 1.1.9.....and now with <1.2.0 being banned on more and more private trackers. Makes me quite frustrated...guess it's cli for awhile

One thing that does help is selecting by tracker or using labels...limits the number of torrents showing up in your current window. Looking forward to the new release and aside from the evil ajax cpu problem...quite happy and content with Deluge.