View previous topic :: View next topic |
Author |
Message |
monsm Guru
Joined: 26 Sep 2007 Posts: 467 Location: London, UK
|
Posted: Sat Oct 17, 2009 8:55 pm Post subject: choosing display manager |
|
|
Hi,
Slight newbie question i guess, but does the display manager do anything after login?
Reason I ask is that I have an old PC (1.2 GHz) and I am interested in maximizing the performance on it. I want to stick with XFCE and I used to have KDE on this machine, so currently I have KDM. I have now removed KDE itself and is using XFCE exclusively, but for now I have kept KDM to log in.
Disk space wise I am ok, so if KDM takes lots of disk space I am not worried, but I am worried about memory and impact on performance after login.
So would my runtime performance be affected if I e.g. switched to SLIM?
Mons |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sat Oct 17, 2009 9:13 pm Post subject: |
|
|
kdm being a kde application, I'd imagine it loads quite a few kde and qt applications, which will absolutely result in wasted memory if you don't make use any other apps using the same shared libs.
Run `ldd /usr/bin/kdm` (path may be different, like sbin rather than bin), this will tell you what libraries kdm loads.
Compare to the output of ldd on the xdm and/or slim binary to see the difference. _________________ "You have to invite me in" |
|
Back to top |
|
|
monsm Guru
Joined: 26 Sep 2007 Posts: 467 Location: London, UK
|
Posted: Sun Oct 18, 2009 6:13 pm Post subject: |
|
|
Hi,
I take it that the display manager only handle login and logout. So that during a session it most likely would be swapped out (if memory was getting tight) and matter very little even on memory usage. Is that correct?
As to slim vs kdm (3.5) I am not convinced slim is any slimmer. Just look at this:
Code: | ldd /usr/kde/3.5/bin/kdm
linux-gate.so.1 => (0xffffe000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7f35000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb7f1a000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7f16000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7f10000)
libpam.so.0 => /lib/libpam.so.0 (0xb7f04000)
libdl.so.2 => /lib/libdl.so.2 (0xb7f00000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb7eeb000)
libutil.so.1 => /lib/libutil.so.1 (0xb7ee7000)
libc.so.6 => /lib/libc.so.6 (0xb7dad000)
/lib/ld-linux.so.2 (0xb8071000) |
Now look at this list for slim:
Code: |
ldd /usr/bin/slim
linux-gate.so.1 => (0xffffe000)
libXft.so.2 => /usr/lib/libXft.so.2 (0xb7f89000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7e6d000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7dea000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7de0000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb7db5000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7d90000)
libz.so.1 => /lib/libz.so.1 (0xb7d7f000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7d4d000)
libXmu.so.6 => /usr/lib/libXmu.so.6 (0xb7d35000)
libjpeg.so.7 => /usr/lib/libjpeg.so.7 (0xb7cff000)
libpam.so.0 => /lib/libpam.so.0 (0xb7cf3000)
libstdc++.so.6 => /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/libstdc++.so.6 (0xb7c06000)
libm.so.6 => /lib/libm.so.6 (0xb7be2000)
libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/libgcc_s.so.1 (0xb7bd4000)
libc.so.6 => /lib/libc.so.6 (0xb7a9a000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb7a7f000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7a7b000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7a74000)
libdl.so.2 => /lib/libdl.so.2 (0xb7a70000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7a4e000)
libXt.so.6 => /usr/lib/libXt.so.6 (0xb79fb000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xb79f2000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xb79d9000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb79c9000)
/lib/ld-linux.so.2 (0xb7fbd000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb79c4000) |
Depends on the size of the files and if these libraries would be loaded by other applications anyway, but still...
Is kdm actually smaller than slim?
Mons |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6103 Location: Dallas area
|
Posted: Sun Oct 18, 2009 6:16 pm Post subject: |
|
|
http://slim.berlios.de/
as far as runtime size, you can't go by the number of libraries that show up in an ldd command.
Edit to add:
I don't run kde but if I wanted to install kdm then this is what would be pulled in
Code: | [ebuild N ] dev-cpp/clucene-0.9.21b USE="-debug -doc -threads" 1,504 kB
[ebuild N ] x11-libs/qt-test-4.5.2 USE="iconv -debug -pch" 0 kB
[ebuild N ] x11-libs/qt-svg-4.5.2 USE="iconv -debug -pch" 0 kB
[ebuild N ] kde-base/qimageblitz-0.0.4 USE="mmx sse sse2 -3dnow (-altivec) -debug" 55 kB
[ebuild N ] kde-base/automoc-0.9.88 9 kB
[ebuild N ] kde-base/oxygen-icons-4.3.1 USE="(-kdeprefix)" 112,625 kB
[ebuild N ] media-libs/raptor-1.4.19 USE="unicode xml -curl -debug" 1,674 kB
[ebuild N ] kde-base/kdebase-pam-7 0 kB
[ebuild N ] virtual/poppler-utils-0.12.0 USE="abiword png" 0 kB
[ebuild N ] x11-libs/qt-opengl-4.5.2-r1 USE="qt3support -debug -pch" 0 kB
[ebuild N ] dev-libs/soprano-2.3.1 USE="clucene dbus java raptor -debug -doc -redland" 1,875 kB
[ebuild N ] app-misc/strigi-0.7.0 USE="clucene dbus fam qt4 -debug -exif -hyperestraier -inotify (-log) -test" 916 kB
[ebuild N ] media-sound/phonon-4.4_pre20090520 USE="gstreamer xcb xine -debug" 570 kB
[ebuild N ] x11-libs/qt-webkit-4.5.2-r1 USE="kde -debug -pch" 0 kB
[ebuild N ] kde-base/kdelibs-4.3.1-r2 USE="acl alsa bzip2 fam handbook mmx nls opengl semantic-desktop spell sse sse2 ssl -3dnow (-altivec) (-aqua) -bindist -debug -doc -jpeg2k (-kdeprefix) -kerberos -openexr -test -zeroconf" 10,265 kB
[ebuild N ] kde-base/libknotificationitem-4.3.1 USE="(-aqua) -debug (-kdeprefix)" 27 kB
[ebuild N ] kde-base/kdebase-data-4.3.1 USE="(-aqua) (-kdeprefix)" 7,091 kB
[ebuild N ] kde-base/kde-env-4.3.1 USE="(-aqua) (-kdeprefix)" 0 kB
[ebuild N ] kde-base/ktimezoned-4.3.1 USE="(-aqua) -debug (-kdeprefix)" 0 kB
[ebuild N ] kde-base/kcheckpass-4.3.1 USE="pam (-aqua) -debug (-kdeprefix)" 60,827 kB
[ebuild N ] kde-base/libkonq-4.3.1 USE="(-aqua) -debug (-kdeprefix) -test" 4,164 kB
[ebuild N ] kde-base/kdesu-4.3.1 USE="handbook (-aqua) -debug (-kdeprefix)" 0 kB
[ebuild N ] kde-base/kdepasswd-4.3.1 USE="handbook (-aqua) -debug (-kdeprefix)" 0 kB
[ebuild N ] kde-base/kdm-4.3.1-r2 USE="consolekit handbook pam (-aqua) -debug (-kdeprefix) -kerberos" 0 kB
Total: 24 packages (24 new), Size of downloads: 201,595 kB
|
and for slim
Code: | [ebuild N ] x11-misc/slim-1.3.1-r4 USE="branding pam -screenshot" 215 kB
[ebuild N ] x11-themes/slim-themes-1.2.3a-r3 6,583 kB
Total: 2 packages (2 new), Size of downloads: 6,798 kB
|
_________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sun Oct 18, 2009 6:28 pm Post subject: |
|
|
Anon-E-moose wrote: | as far as runtime size, you can't go by the number of libraries that show up in an ldd command. | Perhaps, but I have to admit I'm surprised that kdm is not linked to any kde or qt libraries, good move on their part and not what I had expected.
monsm; bearing the above in mind, if you wanted to just stick with kdm just for the sake of convenience I don't think it'll have much impact at all, and you can check how much memory the kdm process is using when you're logged in, what does `ps aux | grep kdm` tell you?
One other thing to check for though, it is possible that kdm starts some kde daemons (and dbus for kde4), so you should also check through the full `ps aux` for such processes... _________________ "You have to invite me in" |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6103 Location: Dallas area
|
Posted: Sun Oct 18, 2009 6:35 pm Post subject: |
|
|
After you get logged in, I think either one would not take up much memory.
I use gdm and it only shows as using appx 6 meg of memory
I'm pretty sure that kdm or slim or any other display manger would be about the same. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
taipan67 l33t
Joined: 04 Dec 2004 Posts: 866 Location: England (i'm told...)
|
Posted: Sun Oct 18, 2009 6:41 pm Post subject: |
|
|
Those "ldd" outputs are extremely surprising - i wonder if kdm builds itself statically against 'qt' and/or 'kde' libs..? If it does, it'd probably be considerably heavier on memory-usage...
I don't know about kdm, but i believe 'gdm' is used after login by xscreensaver if you build it so it's capable of screen-locking and session-switching - so maybe kdm is used similarly by any kde-optimised screensavers that you may or may not have..?
Also, as far as i'm aware, SLiM is no longer being maintained - a couple of other display-managers that hadn't yet hit portage last time i looked are LXDM and Orthos. _________________ "Anyone who goes to see a psychiatrist should have their head examined!" |
|
Back to top |
|
|
monsm Guru
Joined: 26 Sep 2007 Posts: 467 Location: London, UK
|
Posted: Sun Oct 18, 2009 8:01 pm Post subject: |
|
|
Hopeless wrote: | Anon-E-moose wrote: | as far as runtime size, you can't go by the number of libraries that show up in an ldd command. | Perhaps, but I have to admit I'm surprised that kdm is not linked to any kde or qt libraries, good move on their part and not what I had expected.
monsm; bearing the above in mind, if you wanted to just stick with kdm just for the sake of convenience I don't think it'll have much impact at all, and you can check how much memory the kdm process is using when you're logged in, what does `ps aux | grep kdm` tell you?
One other thing to check for though, it is possible that kdm starts some kde daemons (and dbus for kde4), so you should also check through the full `ps aux` for such processes... |
Interesting results on my system:
slim 0.8% of memory
kdm 0.1% of memory
I must admit I am surprised too, quite a difference. Again this is kdm 3.5.10.
Mons |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6749
|
Posted: Sun Oct 18, 2009 8:33 pm Post subject: |
|
|
taipan67 wrote: | Those "ldd" outputs are extremely surprising |
kdm is only the daemon. For the user interface it loads libexec/kdm_greet whose library requirements are more what one expects. Here on kde-4.3.2:
Code: | % ldd /usr/lib64/kde4/libexec/kdm_greet
linux-vdso.so.1 => (0x00007fffe29ff000)
libkdeui.so.5 => /usr/lib64/libkdeui.so.5 (0x00007f7f9916d000)
libQtXml.so.4 => /usr/lib64/qt4/libQtXml.so.4 (0x00007f7f98f30000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f7f98bf8000)
libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007f7f989f2000)
libkdecore.so.5 => /usr/lib64/libkdecore.so.5 (0x00007f7f98570000)
libQtDBus.so.4 => /usr/lib64/qt4/libQtDBus.so.4 (0x00007f7f98316000)
libQtCore.so.4 => /usr/lib64/qt4/libQtCore.so.4 (0x00007f7f97e9c000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f7f97c80000)
libQtSvg.so.4 => /usr/lib64/qt4/libQtSvg.so.4 (0x00007f7f97a36000)
libQtGui.so.4 => /usr/lib64/qt4/libQtGui.so.4 (0x00007f7f96fa2000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.2/libstdc++.so.6 (0x00007f7f96c93000)
libm.so.6 => /lib/libm.so.6 (0x00007f7f96a0f000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f7f967f8000)
libc.so.6 => /lib/libc.so.6 (0x00007f7f96490000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f7f96287000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f7f9606c000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f7f95e5a000)
libXft.so.2 => /usr/lib64/libXft.so.2 (0x00007f7f95c45000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f7f95a42000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f7f9583c000)
libXpm.so.4 => /usr/lib64/libXpm.so.4 (0x00007f7f9562b000)
libQtNetwork.so.4 => /usr/lib64/qt4/libQtNetwork.so.4 (0x00007f7f95336000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f7f9512c000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f7f94f26000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f7f94d1c000)
libz.so.1 => /lib/libz.so.1 (0x00007f7f94b06000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f7f94901000)
librt.so.1 => /lib/librt.so.1 (0x00007f7f946f8000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f7f9440f000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f7f9420b000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f7f93fef000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f7f93ddd000)
liblzma.so.0 => /usr/lib64/liblzma.so.0 (0x00007f7f93bb9000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7f939a0000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f7f93760000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7f99778000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00007f7f93539000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f7f93293000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f7f9308a000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f7f92e4d000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f7f92c48000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f7f92a1c000) |
On the other hand, after logging in, the user face is not needed anymore and probably freed completely. |
|
Back to top |
|
|
monsm Guru
Joined: 26 Sep 2007 Posts: 467 Location: London, UK
|
Posted: Mon Oct 19, 2009 6:20 pm Post subject: |
|
|
mv wrote: | taipan67 wrote: | Those "ldd" outputs are extremely surprising |
kdm is only the daemon. For the user interface it loads libexec/kdm_greet whose library requirements are more what one expects. Here on kde-4.3.2:
Code: | % ldd /usr/lib64/kde4/libexec/kdm_greet
....cut lots of files .... |
On the other hand, after logging in, the user face is not needed anymore and probably freed completely. |
I had a look at the terminal on ctrl+alt+f1 before I logged in. There is indeed a kdm_greet there in addition to the kdm process itself. kdm_greet takes 2.5% on my machine in addition to the 0.1% for kdm itself. Quite clever way of doing it. kdm_greet does indeed disappear after login, so only the small kdm process is left afterwards.
So guess I'll stick with kdm on my xfce system
Mons |
|
Back to top |
|
|
FieserKiller n00b
Joined: 13 May 2004 Posts: 72 Location: Duisburg, Germany
|
Posted: Wed Oct 28, 2009 1:15 am Post subject: |
|
|
FYI (just in case you don't know, you mentioned you are pretty new in linux), if you are worried about memory usage on your system, you can simply don't use any display manager..
in fact, you can go further and dont need any desktop environment at all while you are still not stuck to console applications only.
On my notebook I just start pure X, then xbindkeys, compiz and emerald. thats it..
xbindkeys binds some hotkeys to apps i use frequently (urxvt, firefox, pidgin).
if you need more comfort, just add components like a menu, a taskbar, a file browser, etc..
I heard (although never tried for myself) eg all LXDE components can run stand alone and have a relatively small memory footprint. _________________ I was born at a very young age... |
|
Back to top |
|
|
monsm Guru
Joined: 26 Sep 2007 Posts: 467 Location: London, UK
|
Posted: Wed Oct 28, 2009 9:35 am Post subject: |
|
|
Hi,
I have been around Linux for quite a while already. Never paid much attention to the display manager though.
I'll keep kdm on my system. In fact I just upgraded to the latest KDM 4. The login screen looks great. And the best thing, although kdm_greet is bigger (now 4.3% on my system), kdm itself is still the same at 0.1% memory. That is acceptable given that kdm_greet disappear after login.
I have also heard good things about LXDE. Might give that a try at some point.
Mons |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|