hi
I'm seeing rather high cpu usage from processes that normally don't consume that much power..
Any ideas what might be happening? I upgraded a few days ago to Stoneburner..
see screenshot..
"support report"
hi
I'm seeing rather high cpu usage from processes that normally don't consume that much power..
Any ideas what might be happening? I upgraded a few days ago to Stoneburner..
see screenshot..
"support report"
@jhmiller
Some ideas....
Users running deluge, couch potato, sickbeard not system users.
When i see high cpu it usually is caused by issues with the home directory. I am finding that home directory in most cases should be set to working directory of the application. Is anyone else experiencing high cpu with these applications? With Emby home directory could not be set in postinst because the home directory did not exist yet. The home directory (working directory) was created on first run of the application. Home directory had to be set in mkconf with usermod -d. This is something that should be looked into with each of these applications.
a bit less code to find arch... no uname.
if arch | grep x86_64 >/dev/null 2>&1; then
LIBS_LINK="${LIBS_AMD64}"
echo "cpu 64 bit..."
elif arch | grep 86 >/dev/null 2>&1; then
LIBS_LINK="${LIBS_I386}"
echo "cpu 32 bit..."
elif arch | grep armv7l >/dev/null 2>&1; then
LIBS_LINK="${LIBS_ARMHF}"
echo "cpu armhf..."
else
echo "cpu architecture not supported. exiting..."
exit 0
fi
Alles anzeigen
As with all the plugins I started I just tried what I could at the time, if it worked I left it, you or any one else is more then welcome to make changes where you think it is needed.
I looked over them quickly Miller. I just pointed out some ideas. I had issue with Emby on the home directory and I start to think this is really important on other applications. It is ez to test manually by changing the home directory on a given app giving high cpu. When I fixed this on Emby cpu usage went down over 2/3rds. If you find someone else on github that has done work on same app you can sometimes see if they have done anything with the home directory too.
You are already doing some things different, like system user. So some of the things are just improving old work.
I think the big question is are other people experiencing high cpu on these apps??? If so definitely look at home directory as possible cause.
Never had any issues with high CPU usage with any of the apps I use, admittedly I don't use deluge but the rest are almost always low when ever I check them. My highest item are plex (understandable) and my newsgroup indexer/server (does a lot of work)
The 3 apps use python. If one app has issue if probably will effect the other using python. I would try to check Deluge first. If you know where it has working directory I would have this guy change his home to it. Or check for other projects on github. Maybe you find answer there.
If I were him I would disable those 3 and try running each one alone with the others off. Try to figure out if it is just one or maybe more that is causing the problem.
I looked some more a Deluge. It's home should be here:
/home/deluged/.config/deluge
UMASK=0 # Change this to 0 if running deluged as its own user
PKGNAME=deluge-daemon
SCRIPTNAME=/etc/init.d/$PKGNAME
I will look at it tomorrow as its getting late (early)
I think your suggestion above about running the apps 1 at a time to see if 1 of them is effecting the others is a good one and the best place to start.
It is hard. You really have to install them to check that everything is setting up right. You need another app to test this too.
It was not clear install was finished:
Starting Deluge install process.
Installing libboost-system-dev & libboost-python-dev
Please wait, it can take some time....
Installing libs for a 64 bit system
Selecting previously unselected package libtorrent-rasterbar7.
(Reading database ... 104327 files and directories currently installed.)
Unpacking libtorrent-rasterbar7 (from libtorrent-rasterbar7_0.16.17-1ubuntu3~ppa1~precise_amd64.deb) ...
Setting up libtorrent-rasterbar7 (0.16.17-1ubuntu3~ppa1~precise) ...
Selecting previously unselected package python-libtorrent.
(Reading database ... 104335 files and directories currently installed.)
Unpacking python-libtorrent (from python-libtorrent_0.16.17-1ubuntu3~ppa1~precise_amd64.deb) ...
Setting up python-libtorrent (0.16.17-1ubuntu3~ppa1~precise) ...
Selecting previously unselected package deluge-common.
(Reading database ... 104346 files and directories currently installed.)
Unpacking deluge-common (from deluge-common_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluge-common (1.3.5-0ubuntu2~precise2) ...
Selecting previously unselected package deluge-console.
(Reading database ... 105760 files and directories currently installed.)
Unpacking deluge-console (from deluge-console_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluge-console (1.3.5-0ubuntu2~precise2) ...
Processing triggers for man-db ...
Selecting previously unselected package deluge-web.
(Reading database ... 105812 files and directories currently installed.)
Unpacking deluge-web (from deluge-web_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluge-web (1.3.5-0ubuntu2~precise2) ...
Processing triggers for man-db ...
Selecting previously unselected package deluge-gtk.
(Reading database ... 107857 files and directories currently installed.)
Unpacking deluge-gtk (from deluge-gtk_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluge-gtk (1.3.5-0ubuntu2~precise2) ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Processing triggers for mime-support ...
Selecting previously unselected package deluge.
(Reading database ... 107998 files and directories currently installed.)
Unpacking deluge (from deluge_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluge (1.3.5-0ubuntu2~precise2) ...
Processing triggers for man-db ...
Selecting previously unselected package deluged.
(Reading database ... 108007 files and directories currently installed.)
Unpacking deluged (from deluged_1.3.5-0ubuntu2~precise2_all.deb) ...
Setting up deluged (1.3.5-0ubuntu2~precise2) ...
Processing triggers for man-db ...
upgrades to 2 packages
Setting up libtorrent-rasterbar7 (0.16.18-1~bpo70+1) ...
Setting up python-libtorrent (0.16.18-1~bpo70+1) ...
Home directory:
root@stoneburnervm:/# cat /etc/passwd | grep deluge-daemon
deluge-daemon:x:1003:100::/home/deluge-daemon:/usr/sbin/nologin
root@stoneburnervm:/# id deluge-daemon
uid=1003(deluge-daemon) gid=100(users) groups=100(users)
Very low cpu... but not connected
Looks pretty normal. Home directory is ok and config files there.
I think it is user error. He probably has a permissions problem. Deluge is working fine.
Hi
There aren't any permission errors.
I think it might've been a fluke (that travelled through reboots). Things have settled down now and isn't using that much CPU.
I just couldn't understand why the high cpu usage continued for so long.. AND continued after reboot..
But it might've been python related since all apps are using python...
If you are getting high cpu lower your max download rate. Transmission is using less cpu at same download bandwidth. I have both set to max download at 1024 kb/s in the picture.
There is a discussion on the forums for Deluge regarding high cpu. This problem has been going on for some time with Deluge.
http://forum.deluge-torrent.org/viewtopic.php?f=7&t=46289
http://forum.deluge-torrent.org/viewtopic.php?f=7&t=43547
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!