#1233 closed feature-request (Invalid)
bring deluge demon to C language and enable web interface reverse proxying
Reported by: | maxadamo | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.3 |
Component: | Unknown | Version: | 1.2.3 |
Keywords: | Cc: |
Description
Hi. I love deluge. It's a perfect software. But as I prefer to use torrent as a daemon, where I can connect thru the interface, I abandoned deluge as it uses too much CPU. Now I started using Transmission. Even if I am not downloading any file, I see the demon goes at 4%, 5% of CPU usage. This is the disadvantage of writing demon/sockets with python.
Furthermore, the web interface of Transmission can be reverse proxied without any problem. As you understand, from many places where you connect thru proxies, it's impossible to reach other ports than 80 and 443. For this reason is important to have the possibility to use reverse proxies.
Change History (3)
comment:1 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
Of course I am waiting 1.3 and I'll try it _ I kindly ask you to bring 1.3 to Ubuntu PPA as soon as you can.
By the way: 5% of CPU usage, when the demon is idle, is not fine: it uses more CPU than RDBMS, or web server. I hope the new version has reduced this problem.
Right now - from this point of view - transmission is really great, and *ALL* other P2P software have the same issue like deluge: they use lot of CPU. mldonkey uses much cpu, original bittorrent is python and uses really a lot of cpu, and I prefer not to talk about vuze ....
cheers
comment:3 by , 14 years ago
Here is 1.3 running for me.
$ ps aux | head -1 && ps aux | grep deluge USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND damien 21144 1.0 0.6 242564 24932 pts/0 Sl+ 15:53 0:01 /usr/bin/python /usr/bin/deluged -d damien 21262 3.4 0.6 142352 26960 pts/2 S+ 15:54 0:01 /usr/bin/python /usr/bin/deluge-web
We won't be rewriting deluged in C, and the webui is capable of being reversed proxied in master/1.3, please check other tickets before filing a new one.
There has been some improvements in cpu/mem usage for 1.3 so I would check give that a try first.