[SOLVED] RAM usage in Openbox/E17

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] RAM usage in Openbox/E17

Postby clancularius » Oct 19th, '13, 19:34

I recently did a fresh install of Mageia3 (32 Bit), installing pretty much everything the DVD had to offer, including all the DE (KDE,LDXE,Xfce,Gnome,E17,Openbox etc.) so that I have a fully loaded distro with all software pre-installed while I stick to E17 or Openbox. The problem I face is that when I get into Openbox or E17 I still have a lot of RAM already being used by apps which probably are not needed (300+ MB on a 1 GB system :shock: ). I have uploaded a screenshot of LXtask showing all the tasks running.

If I'm not wrong net_applet, nm-applet, NetworkManager all running (please refer the attached image) are to serve the same purpose but are associated with different DE.

Similarly mgaapplet and applet.py do the same job.

How and Which services/software I should stop to get the RAM usage to about 130 MB (which it used to be on the same machine while running Mageia2 with similar installation). I need a way which would work in both E17 and Openbox (and preferable not affect the other DE)
Attachments
ss.png
LXtask Screenshot
ss.png (138.39 KiB) Viewed 1327 times
Last edited by clancularius on Oct 21st, '13, 20:24, edited 1 time in total.
clancularius
 
Posts: 4
Joined: Oct 19th, '13, 18:51

Re: RAM usage in Openbox/E17

Postby doktor5000 » Oct 21st, '13, 13:11

Please show the output of
Code: Select all
ps -ef
as screenshots are not that good for such things ;)

From a quick look, here's a list of things which you can kill or replace by something which is not as memory-intensive:

mgaapplet
net_applet
nm-applet
konsole
colord-sane
NetworkManager
colord
modem-manager
kdm

Also, for an minimal install like you want it, better approach is to use the DualArchCD and then add what is missing,
not install everything on the normal DVD and then slim it down
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18073
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: RAM usage in Openbox/E17

Postby clancularius » Oct 21st, '13, 16:59

I don't actually want a minimal install , but a minimal session in which i can use the software which come with other DE but independent of the DE (for instance using thunar,Knotes,K3B,etc in Openbox) which I agree is more of a privilege than necessity.Also handpicking and installing these apps on a minimal install would be more time consuming and would require most of the libraries anyways.

I always thought that most of the startup apps were DE dependent and so KDE stuff wont auto start in Gnome or XFCE unless explicitly made to do so. (also on my previous install of Mageia 2 on same machine I dint face these problems)

I have pasted the output pf ps -ef below.

Code: Select all
[clancularius@localhost ~]$ ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 19:38 ?        00:00:00 /sbin/init
root         2     0  0 19:38 ?        00:00:00 [kthreadd]
root         3     2  0 19:38 ?        00:00:00 [ksoftirqd/0]
root         5     2  0 19:38 ?        00:00:00 [kworker/0:0H]
root         6     2  0 19:38 ?        00:00:00 [kworker/u:0]
root         7     2  0 19:38 ?        00:00:00 [kworker/u:0H]
root         8     2  0 19:38 ?        00:00:01 [migration/0]
root         9     2  0 19:38 ?        00:00:00 [rcu_bh]
root        10     2  0 19:38 ?        00:00:00 [rcu_sched]
root        11     2  0 19:38 ?        00:00:00 [ksoftirqd/1]
root        12     2  0 19:38 ?        00:00:01 [migration/1]
root        14     2  0 19:38 ?        00:00:00 [kworker/1:0H]
root        15     2  0 19:38 ?        00:00:00 [cpuset]
root        16     2  0 19:38 ?        00:00:00 [khelper]
root        17     2  0 19:38 ?        00:00:00 [kdevtmpfs]
root        18     2  0 19:38 ?        00:00:00 [netns]
root        19     2  0 19:38 ?        00:00:00 [bdi-default]
root        20     2  0 19:38 ?        00:00:00 [kintegrityd]
root        21     2  0 19:38 ?        00:00:00 [kblockd]
root        22     2  0 19:38 ?        00:00:00 [ata_sff]
root        23     2  0 19:38 ?        00:00:00 [md]
root        24     2  0 19:38 ?        00:00:00 [devfreq_wq]
root        27     2  0 19:38 ?        00:00:00 [khungtaskd]
root        28     2  0 19:38 ?        00:00:00 [kswapd0]
root        29     2  0 19:38 ?        00:00:00 [ksmd]
root        30     2  0 19:38 ?        00:00:00 [khugepaged]
root        31     2  0 19:38 ?        00:00:00 [fsnotify_mark]
root        32     2  0 19:38 ?        00:00:00 [crypto]
root        38     2  0 19:38 ?        00:00:00 [kthrotld]
root        40     2  0 19:38 ?        00:00:00 [scsi_eh_0]
root        41     2  0 19:38 ?        00:00:00 [scsi_eh_1]
root        42     2  0 19:38 ?        00:00:00 [scsi_eh_2]
root        43     2  0 19:38 ?        00:00:00 [scsi_eh_3]
root        44     2  0 19:38 ?        00:00:00 [kpsmoused]
root        45     2  0 19:38 ?        00:00:01 [kworker/1:2]
root        48     2  0 19:38 ?        00:00:00 [kworker/u:4]
root        50     2  0 19:38 ?        00:00:00 [deferwq]
root        88     2  0 19:38 ?        00:00:00 [scsi_eh_4]
root        89     2  0 19:38 ?        00:00:00 [scsi_eh_5]                                                                                                 
root       264     2  0 19:38 ?        00:00:00 [firewire]                                                                                                   
root       270     2  0 19:38 ?        00:00:00 [khubd]                                                                                                     
root       271     2  0 19:38 ?        00:00:00 [kworker/0:1H]
root       342     2  0 19:38 ?        00:00:00 [jbd2/sdb1-8]
root       343     2  0 19:38 ?        00:00:00 [ext4-dio-unwrit]
root       371     2  0 19:38 ?        00:00:00 [kworker/1:1H]
root       380     1  0 19:38 ?        00:00:00 /usr/lib/systemd/systemd-journald
root       381     2  0 19:38 ?        00:00:00 [kauditd]
root       383     1  0 19:38 ?        00:00:00 /usr/lib/systemd/systemd-udevd
root       397     2  0 19:38 ?        00:00:00 [flush-8:16]
root       416     2  0 19:38 ?        00:00:00 [rpciod]
root       506     2  0 19:38 ?        00:00:00 [kmemstick]
root       507     2  0 19:38 ?        00:00:00 [r592_io]
root       508     2  0 19:38 ?        00:00:00 [r852]
root       522     2  0 19:38 ?        00:00:00 [cfg80211]
root       524     2  0 19:38 ?        00:00:00 [hd-audio0]
root       531     2  0 19:38 ?        00:00:00 [iwl3945]
root       574     2  0 19:39 ?        00:00:00 [jbd2/sdb6-8]
root       575     2  0 19:39 ?        00:00:00 [ext4-dio-unwrit]
root       814     1  0 19:39 ?        00:00:00 /usr/lib/systemd/systemd-logind
root       817     1  0 19:39 ?        00:00:00 /usr/libexec/udisks-daemon --no-debug --replace
499        823     1  0 19:39 ?        00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root       825     1  0 19:39 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon
root       826     1  0 19:39 ?        00:00:00 /usr/sbin/cupsd -f
avahi      827     1  0 19:39 ?        00:00:00 avahi-daemon: running [linux-2.local]
root       830     1  0 19:39 ?        00:00:00 /usr/libexec/upowerd
avahi      840   827  0 19:39 ?        00:00:00 avahi-daemon: chroot helper
root       846     1  0 19:39 ?        00:00:00 /usr/sbin/crond -n
root       856     1  0 19:39 ?        00:00:00 /usr/bin/kdm -nodaemon
root       883     1  0 19:39 ?        00:00:00 /usr/sbin/acpid
root       919   817  0 19:39 ?        00:00:00 udisks-daemon: not polling any devices         
root       930   856  6 19:39 tty1     00:01:14 /etc/X11/X :0 vt1 -nolisten tcp -auth /var/run/xauth/A:0-ydYkgc
root       932     1  0 19:39 ?        00:00:00 /usr/sbin/nscd
root       938     1  0 19:39 ?        00:00:00
root       940     1  0 19:39 ?        00:00:00 /usr/bin/speech-dispatcher -d
polkitd    946     1  0 19:39 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
root       947     1  0 19:39 ?        00:00:00 /usr/libexec/colord
root       975     1  0 19:39 ?        00:00:00 /usr/sbin/modem-manager
root       978     1  0 19:39 ?        00:00:00 /usr/sbin/bluetoothd -n
root      1073     1  0 19:39 ?        00:00:00 /usr/libexec/colord-sane
root      1110   856  0 19:39 ?        00:00:00 -:0                   
rpc       1399     1  0 19:39 ?        00:00:00 /sbin/rpcbind -w
root      1401     1  0 19:39 ?        00:00:00 /usr/sbin/rpc.idmapd
rpcuser   1407     1  0 19:39 ?        00:00:00 /sbin/rpc.statd
root      2127     1  0 19:39 ?        00:00:00 /usr/sbin/mandi -d
500       2135  1110  0 19:39 ?        00:00:00 /usr/bin/enlightenment_start
500       2165     1  0 19:39 ?        00:00:00 gpg-agent --keep-display --daemon --write-env-file /home/clancularius/.gnupg/gpg-agent-info
500       2200     1  0 19:39 ?        00:00:00 /usr/bin/dbus-launch --exit-with-session --sh-syntax
500       2201     1  0 19:39 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
500       2207     1  0 19:39 ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
rtkit     2208     1  0 19:39 ?        00:00:00 /usr/libexec/rtkit-daemon
500       2216  2207  0 19:39 ?        00:00:00 /usr/libexec/pulse/gconf-helper
500       2218     1  0 19:39 ?        00:00:00 /usr/libexec/gconfd-2
500       2238     1  0 19:39 ?        00:00:00 /usr/libexec/gvfsd
500       2250  2135  0 19:39 ?        00:00:00 [xdg-user-dirs-g] <defunct>
500       2255     1  0 19:39 ?        00:00:00 s2u --daemon=yes
500       2256  2135  7 19:39 ?        00:01:26 /usr/bin/enlightenment
500       2279  2256  0 19:39 ?        00:00:00 /usr/lib/enlightenment/modules/temperature/linux-gnu-i586-0.17.1/tempget 0 (null) 128
500       2282  2256  0 19:39 ?        00:00:00 /usr/lib/enlightenment/utils/enlightenment_fm
500       2399     1  0 19:41 ?        00:00:00 /usr/libexec/at-spi-bus-launcher
500       2456     1  0 19:42 ?        00:00:00 /usr/lib/xfce4/xfconf/xfconfd
500       2458     1  0 19:42 ?        00:00:00 /usr/libexec/gvfs-udisks2-volume-monitor
root      2460     1  0 19:42 ?        00:00:00 /usr/lib/udisks2/udisksd --no-debug
500       2469     1  0 19:42 ?        00:00:00 /usr/libexec/gvfs-afc-volume-monitor
500       2474     1  0 19:42 ?        00:00:00 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
root      2586     2  0 19:44 ?        00:00:00 [kworker/0:0]
root      2641     2  0 19:49 ?        00:00:01 [kworker/0:2]
500       2946     1  0 19:51 ?        00:00:00 kdeinit4: kdeinit4 Running...
500       2948  2946  0 19:51 ?        00:00:00 kdeinit4: klauncher [kdeinit] --fd=8
500       2950     1  0 19:51 ?        00:00:00 kdeinit4: kded4 [kdeinit] 
500       2952     1  0 19:51 ?        00:00:00 /usr/libexec/gam_server
root      2966     2  0 19:54 ?        00:00:00 [kworker/1:0]
root      2967     2  0 19:54 ?        00:00:00 [kworker/0:1]
500       2985     1  0 19:57 ?        00:00:00 /usr/lib/tumbler-1/tumblerd
root      2995     2  0 19:57 ?        00:00:00 [flush-8:0]
500       3120  2256  6 19:59 ?        00:00:00 /home/clancularius/iron-linux/iron.sh
500       3121  3120  0 19:59 ?        00:00:00 /home/clancularius/iron-linux/iron.sh
500       3122  3120  0 19:59 ?        00:00:00 /home/clancularius/iron-linux/iron.sh --type=zygote
500       3133  3122  0 19:59 ?        00:00:00 [iron.sh] <defunct>
500       3156  3122  3 19:59 ?        00:00:00 /home/clancularius/iron-linux/iron.sh --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/d
500       3196     1  8 19:59 ?        00:00:00 konsole
500       3198  3196  1 19:59 pts/0    00:00:00 /bin/bash
500       3231  3198  0 19:59 pts/0    00:00:00 ps -ef
[clancularius@localhost ~]$


If I disable some of the services from MCC would they be disabled even when I log into other DE ? Can I not make the services specific to the DE so that KDE services start only when in KDE session, same with Gnome and others, and when I use E17 or Openbox I can specify what to run. Thus maintaining the integrity of DE.
clancularius
 
Posts: 4
Joined: Oct 19th, '13, 18:51

Re: RAM usage in Openbox/E17

Postby doktor5000 » Oct 21st, '13, 17:39

Well, that's not that easy, you have to edit all programs/services to only start in those DEs where you want them to start.
But for that you have to track down where the apps are started. Are they started with your x session that would be in /etc/X11/xinit.d/ (e.g. mgaapplet)
or are they started from the systemwide autostart /etc/xdg/autostart/ (e.g. net_applet) or are they started in general during system boot (networkmanager) or with your desktop session, or with your display manager.

If the programs are started by .desktop files, there are dedicated options for what you want, e.g take a look at this:
Code: Select all
[doktor5000@localhost ~]$ grep -Ri only /etc/xdg/autostart/
/etc/xdg/autostart/xscreensaver.desktop:OnlyShowIn=XFCE;
/etc/xdg/autostart/gsettings-data-convert.desktop:OnlyShowIn=GNOME;Unity;
/etc/xdg/autostart/gnome-keyring-secrets.desktop:OnlyShowIn=GNOME;Unity;MATE;
/etc/xdg/autostart/gnome-keyring-ssh.desktop:OnlyShowIn=GNOME;Unity;MATE;
/etc/xdg/autostart/xfsettingsd.desktop:OnlyShowIn=XFCE;
/etc/xdg/autostart/at-spi-registryd.desktop:OnlyShowIn=GNOME;
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop:OnlyShowIn=GNOME;Unity;MATE;
/etc/xdg/autostart/at-spi-dbus-bus.desktop:OnlyShowIn=GNOME;Unity;
/etc/xdg/autostart/xfce4-power-manager.desktop:OnlyShowIn=XFCE;
/etc/xdg/autostart/gnome-keyring-gpg.desktop:OnlyShowIn=GNOME;Unity;MATE;
/etc/xdg/autostart/pam-panel-icon.desktop:OnlyShowIn=GNOME;KDE;XFCE;
/etc/xdg/autostart/pulseaudio-kde.desktop:OnlyShowIn=KDE;


Should be pretty self-explanatory, they available keys are listed here: http://standards.freedesktop.org/menu-s ... t/apb.html
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18073
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: RAM usage in Openbox/E17

Postby clancularius » Oct 21st, '13, 19:23

That seems to be doable but time consuming for noob like me (finding out what services do what). Luckily it seems most of the services are started by ".desktop" files but the keyword "OnlyShowIn" needs to be added to many of them.I will probably start with only the resource hungry services which will hopefully give me optimal result with minimal effort ;) .

Thanks for the help so far.If its not asking too much (I know I'm pushing my luck), could you please point out the services which are duplicated (like one doing the same job but for different DE which are running simultaneously) so for the time being I can disable them till I can get things sorted out. The resource hungry ones should be more than enough for now. I just want to be sure that by turning some services off, I could still use the system with all the software without any problems.(my worry is if I shut down some kde service will my kde apps work fine?)
clancularius
 
Posts: 4
Joined: Oct 19th, '13, 18:51

Re: RAM usage in Openbox/E17

Postby doktor5000 » Oct 21st, '13, 19:56

clancularius wrote:Thanks for the help so far.If its not asking too much (I know I'm pushing my luck), could you please point out the services which are duplicated (like one doing the same job but for different DE which are running simultaneously) s


Sorry, i'm not interested in running several different DEs only to compare which services are of duplicate functionality.
You wanted this special "cleaned" desktop session or multiple of those so you have to invest time for that.

Can't see the use of that, it would be a much more sane approach to only have one desktop, and slim it down as much as you can.
It's also quite useless to run something like LXDE or even only openbox, but use konsole/k3b, which pulls in all the overhead of KDE libraries
and defeats the purpose of running slimmer DEs.

You probably should make up your mind what you really want.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18073
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: RAM usage in Openbox/E17

Postby clancularius » Oct 21st, '13, 20:23

Thanks for the help.I do realize the point you are making.
One thing I don't understand is that what has changed in Mageia3 , because using Magea2 with a similar install everything was perfect right out of the box.I have installed additional DE this time (E17 and Xfce) but I don't think that has anything to do with this.

Any ways I am going to give your methods and suggestion a try. First I will try to manually make the service DE specific and if I fail at that, probably get rid of the other DE.

Thanks once again ...

Time to mark this thread as SOLVED :)
clancularius
 
Posts: 4
Joined: Oct 19th, '13, 18:51

Re: [SOLVED] RAM usage in Openbox/E17

Postby doktor5000 » Oct 21st, '13, 21:16

Well, the only thing could be networkmanager, which is pulled in by either GNOME or if something pulls in some gnome dependencies.
As networkmanager is running when installed, even if you don't use it, you should get rid of it. Either disable it starting at all or remove it,
same for modem-manager.

Apart from that, net_applet and mgaapplet are good candidates which use quite a lot of memory, and
can be replaced by manual updates and using another network manager applet or not using one at all. You may lose
some convenience that way.

Also journalctl (the journal replacing traditional syslog) seems to use ~276 MB shared memory, you can save a little bit there.
journalctl is also the default since Mageia 3.

But that's what I meant with the question what you expectation/approach is. If you only want to save RAM, there's a ton of things
you don't need or can be replaced by something else. But you may lose convenience that way, depends what you really want to achieve.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18073
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest