Deluge
Hi all,
My deluge daemon takes a huge amount of memory and in rare case it took so much memory that it cause my server to run out of memory and OOM killer kicked in.
I'm running Deluge 1.3.1 on a Debian Sid (with 1.5gb of ram) and libtorrent-rasterbar5 (0.14.10-2+b1).
If my torrent count goes around 80, deluge takes between 800mb and 1.1gb (in rare cases it grown above 1.1gb and eventually triggered kernel OOM killer);
I've brought the torrent count down to 30, and now it's taking between 400 to 600mb.
This memory usage seems quite high and is giving me lots of grief.
How can i reduce this massive memory usage? ( Or are these values normal?)
Thanks.
Huge memory usage - Deluge 1.3.1
Re: Huge memory usage - Deluge 1.3.1
Is it the gtk client or the daemon using the memory? I have about 1,700 torrents running and deluge itself is only using 2.3% of my RAM so that's about 368MB used. If I attempt to run the gtk client however things are not so pretty and it just locks up within a few minutes. You may want to try using deluge-console, it's using about 64MB of RAM on my machine.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
michael 4921 27.7 2.3 624528 382716 ? Sl 15:50 130:29 /usr/bin/python /usr/bin/deluged --port=58846 --config=/home/.../.config/deluge
michael 10322 0.9 0.4 115800 69300 pts/9 S+ 17:26 3:31 /usr/bin/python /usr/bin/deluge-console
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
michael 4921 27.7 2.3 624528 382716 ? Sl 15:50 130:29 /usr/bin/python /usr/bin/deluged --port=58846 --config=/home/.../.config/deluge
michael 10322 0.9 0.4 115800 69300 pts/9 S+ 17:26 3:31 /usr/bin/python /usr/bin/deluge-console
Re: Huge memory usage - Deluge 1.3.1
It's actually deluged taking all that memory (the gtk client is on a different machine). I'm running a headless server.
I've upgraded to librasterbar6 (0.15) and memory usage seems to be better but still high. Now takes longer to get to 400mb but still gets there. I've also lowered the Cache Size to "2000" blocks (not exactly sure if this helped or not).
All and all, i have 31 torrents and deluged is now taking 350mb - which is still massively high when compered to your (taking the same with 1700 torrents).
Deluged uptime is about 1 week.
I connect the gtk client to deluged for a few minutes per day, to download a few torrents and delete others.
I've tried to use the web-ui instead of the gtk (for a week or so) but i've seen no difference in memory usage.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26456 azureus 20 0 438m 345m 4088 S 12 23.0 726:20.48 /usr/bin/python /usr/bin/deluged
I've upgraded to librasterbar6 (0.15) and memory usage seems to be better but still high. Now takes longer to get to 400mb but still gets there. I've also lowered the Cache Size to "2000" blocks (not exactly sure if this helped or not).
All and all, i have 31 torrents and deluged is now taking 350mb - which is still massively high when compered to your (taking the same with 1700 torrents).
Deluged uptime is about 1 week.
I connect the gtk client to deluged for a few minutes per day, to download a few torrents and delete others.
I've tried to use the web-ui instead of the gtk (for a week or so) but i've seen no difference in memory usage.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26456 azureus 20 0 438m 345m 4088 S 12 23.0 726:20.48 /usr/bin/python /usr/bin/deluged