FEB
14
2010

Exmap fixed, and a little resulting peek at memory usage

I have fixed Exmap, my still favourite tool to measure system memory usage, to compile with latest kernels, and also to work on x86_64 (the latter was a bit of guess-work, but I think I got it right). KSysGuard seems to be getting close, and with Exmap unmaintained by its author :( I don't feel like doing this forever, but for now, it's still possible to get exmap from my home:llunak:kernel repository. And as I don't feel like trying to do cross-distro kernel packages in the buildservice, those not using openSUSE are left with either trying to package it for their other distro, or pick out the patches from the .src.rpm .

While I was at it, I had just a little look at memory usage. Since I had done quite some comparisons of KDE3's memory usage with other desktops in the past, the first thing that came to my mind was doing that quickly again. As these days LXDE appears to be the new lightweight kid on the block, I tried that one, and also Xfce. Finally there's TWM, basically just to show the memory usage without any desktop. All of them are default desktops on openSUSE 11.2 for a new user with a file browser and terminal open, the only exceptions being adding a mixer to the default Xfce setup for a reason that will be obvious later and not using the nvidia driver. LXDE is from the X11:lxde repo, KDE version is 4.3.5 that'll soon end up in an online update. So, here it is (for those who don't want to find out what all those values mean, the most important number here is the 'Effective Resident TOTALS').




Of course, this is not really comparable to my old memory usage test, for a number of reasons, such as this being x86_64 machine, the setup being different, and so on.

It's interesting to note that LXDE actually loses to Xfce. That 'python' there is in fact GMixer. That really shows that you don't get lightweight things unless you check the setup yourself. And it probably also shows that you can get lightweight things only if also your expectations are lightweight.

It also shows that KDE4's memory usage is not as bad some some might think, although it would be nice if somebody would be bored enough to analyse it in more detail. There seem to be enough people bored enough to just complain about KDE4 performance but not do anything else, and this is actually pretty simple. Or do you need an Akademy talk for that or what?

Comments

That would be a perfect topic I guess =:). Interesting even!

/me encourages Lubos to send in a proposal to akademy-talks[AT]kde[DOT]org.


By Bertjan Broeksema at Mon, 02/15/2010 - 08:55

I get more or less the same numbers in KSysGuard for plasma-desktop at the start. The problem is that plasma-desktop seems to have memory leaks and it can eat over 100 or 200 Mbs. of memory after several days of uninterrupted usage (I think Plasma folks are aware of the issue so I guess it will eventually be solved).

I mention it because that would explain why people complain about KDE 4 SC performance: the desktop feels fast at login but the experience is degraded as you use it for a long time.


By Álvaro Manuel Recio Pérez at Mon, 02/15/2010 - 12:02

to me the problem is not gmixer... i wonder if the problem can be the trash support patch we added to pcmanfm..

do you want to help us to figure it out?

regards
Andrea (openSUSE-LXDE, project admin)


By anubisg1 at Wed, 02/17/2010 - 16:22

I'm afraid I don't have the time for that, but the howto linked from the post (last link) should have all one needs for figuring out memory usage.


By Lubos Lunak at Wed, 02/17/2010 - 16:52