Comments on: KDE vs XFCE in terms of memory usage http://blog.bauermann.eng.br/2008/01/06/kde-vs-xfce-in-terms-of-memory-usage/ incomplete and abridged Sat, 08 May 2010 06:36:47 +0000 hourly 1 http://wordpress.com/ By: bauermann http://blog.bauermann.eng.br/2008/01/06/kde-vs-xfce-in-terms-of-memory-usage/#comment-19 bauermann Tue, 08 Jan 2008 02:44:29 +0000 http://blog.bauermann.eng.br/2008/01/06/kde-vs-xfce-in-terms-of-memory-usage/#comment-19 Thanks for the link, that's very interesting read indeed. It seems my method for evaluating memory use is even lamer than I thought it was. :-) And Lubos got quite different results for the "plain desktop" case, which was what I was trying to measure. But he was using an older XFCE version, maybe things changed in that project since then... About using lots of shared libraries, it's good from the memory usage and code reuse perspective, but the downside is that it's lots of work for the dynamic linker and can have a measurable impact in program loading, as shown by Ulrich Drepper: http://people.redhat.com/drepper/dsohowto.pdf Prelinking can help, but not if libraries are dlopened (I don't know if KDE uses dlopen very much). Thanks for the link, that’s very interesting read indeed.

It seems my method for evaluating memory use is even lamer than I thought it was. :-) And Lubos got quite different results for the “plain desktop” case, which was what I was trying to measure. But he was using an older XFCE version, maybe things changed in that project since then…

About using lots of shared libraries, it’s good from the memory usage and code reuse perspective, but the downside is that it’s lots of work for the dynamic linker and can have a measurable impact in program loading, as shown by Ulrich Drepper:

http://people.redhat.com/drepper/dsohowto.pdf

Prelinking can help, but not if libraries are dlopened (I don’t know if KDE uses dlopen very much).

]]> By: SSJ http://blog.bauermann.eng.br/2008/01/06/kde-vs-xfce-in-terms-of-memory-usage/#comment-18 SSJ Mon, 07 Jan 2008 16:17:10 +0000 http://blog.bauermann.eng.br/2008/01/06/kde-vs-xfce-in-terms-of-memory-usage/#comment-18 "One explanation would be that KDE actually shares more memory between processes than XFCE. " You might want to read Lubos Lunak's (kwin developer) analysis of memory usage: http://ktown.kde.org/~seli/memory/desktop_benchmark.html In short - yes, KDE is famed for its excellent adherence to the Once-And-Once-Only ( http://en.wikipedia.org/wiki/Don't_repeat_yourself ) philosophy, with huge amounts of functionality crammed into shared libraries, resulting in apps that have a smaller Lines of Code count and just much less duplication and more efficiency in general. “One explanation would be that KDE actually shares more memory between processes than XFCE. ”

You might want to read Lubos Lunak’s (kwin developer) analysis of memory usage:

http://ktown.kde.org/~seli/memory/desktop_benchmark.html

In short – yes, KDE is famed for its excellent adherence to the Once-And-Once-Only ( http://en.wikipedia.org/wiki/Don‘t_repeat_yourself ) philosophy, with huge amounts of functionality crammed into shared libraries, resulting in apps that have a smaller Lines of Code count and just much less duplication and more efficiency in general.

]]>