From kde-devel Thu Jul 16 19:24:40 2009 From: John Tapsell Date: Thu, 16 Jul 2009 19:24:40 +0000 To: kde-devel Subject: Re: KDE4 is a memory hog Message-Id: <43d8ce650907161224i3b91dc1nf69941d569339896 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-devel&m=124777293825130 2009/7/16 Ferdinand Gassauer : > On Tuesday 14 July 2009 15:58:48 Thiago Macieira wrote: > just want to say that after installing the latest Factory builds KDE bacame > really snappy. - and much reduced memory requirements and much more shared mem > used. For what it's worth, I don't actually know what the shared mem used column actually shows. Or even the memory column. (The memory column is RSS - SHR. The shared memory column is SHR. But past that, the numbers are still kinda meaningless...) John >> Em Terça-feira 14 Julho 2009, às 10:40:11, Ferdinand Gassauer escreveu: >> > On Monday 13 July 2009 23:27:13 Thiago Macieira wrote: >> > > The use of MySQL in Amarok and Akonadi increases the memory usage by >> > > another 30 MB (just by starting MySQL). The use of the NVidia driver >> > > consumes another 10 MB *per* *process*: amarok, plasma, ksmserver, kwin >> > > (unless you're using KDE 4.3). >> > >> > I just uninstalled the nvidia driver .... - seems that memory consumption >> > decreases and preceived speed increases significantly (due to no more >> > swaping) >> >> Swapping shouldn't be an issue, but memory consumption definitely. >> >> First of all, don't use the NVidia driver with KDE 4.2. Use 4.3, since it >> includes Luboš's fix to share it. (so instead of having 3 or 4 applications >> with libGL.so loaded, we have ALL KDE applications doing that, but sharing >> it) >> >> Second, I think that the most memory used by X and by kwin is due to pixmap >> caching. Then remember Qt applications do double-buffering too, which leads >> to triple buffering of everything. There was even a bug in Oxygen that >> caused KWin to enable double-buffering of its own, which would lead to >> quadruple-buffering, but I think that has been fixed for a year. >> >> If you run xrestop, you'll see the number of pixmaps in use. Up until last >> week, plasma would leak a lot of pixmaps. KWin too, until this weekend in >> trunk. Those leakages cause the process memory space to grow as well as X's >> own. >> >> Since Plasma and KWin were fixed, the biggest aggressors for me are Kontact >> (mostly Akregator, which btw can't do KIO correctly, launching a hundred >> kio_http) and Skype. Now, we can't fix Skype unless it's a leak inside Qt, >> but Kontact we can. >> >> res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier >> 4200000    45   39    0 2569 2677    42744K     64K  42809K 30060 skype >> 4c00000    29    9    0  614  852     8877K     20K   8898K 23117 E-mail - >> Kontact >> >> (this kontact is not running akregator; if I run it, it eventually exhausts >> the X pixmap memory) >> >> In my current setup, X is holding 128 MB of pixmaps. So no wonder: >> >> F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME >> COMMAND 4     0  7760  5810  20   0 524676 184420 poll_s Ss+ tty7 >> 571:56 /etc/X11/X > > -- > cu > ferdinand > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<