[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kde, xfree & RAM
From:       Allan Sandfeld Jensen <kde () carewolf ! com>
Date:       2004-06-10 21:53:00
Message-ID: 200406102353.00457.kde () carewolf ! com
[Download RAW message or body]

On Thursday 10 June 2004 01:28, Michael Pyne wrote:
> On Wednesday 09 June 2004 19:11, Jean-Philippe Schneider wrote:
> > Hi,
> >
> > In seeing table in ksysguard, i was stomached... For example i saw that
> > kopete takes 40Mo of physical mem and 60 of virtual...
> > Is that normal??? Ithink it is a little bit heavy!
> > If someone could explain me ;)
>
> It's a common misperception, because of the way memory reporting works
> under Linux.
>
> The physical memory and virtual memory reports include not only Kopete, but
> any shared libraries it may be using.  This includes glibc, Internet
> support, and KDE too, of course. ;-)
>
> Don't worry, though.  Most of that memory is shared by Linux between
> programs. So if you started up Kopete again, it doesn't double the memory
> use.
>
> If you'd like to see how much memory there is left, there should be a
> module for that in ksysguard, or you can just use the free command from the
> shell.
>
Find the proces-nr using "ps -aF | grep <insert application-name>" then type 
"cat proc/<processnr>/status" look for the lines that looks like this:
VmSize:    48620 kB
VmLck:         0 kB
VmRSS:     29844 kB
VmData:     7984 kB
VmStk:        40 kB
VmExe:        40 kB
VmLib:     30956 kB

This is the result of a "konqueror --preload" on my installation where 
debug-info is enable. It tells us that konqueror has linked to 20Mbyte of 
libraries, and uses around 8Mbyte itself. VmSize and VmRSS typically reported 
by ksysguard or top are useless.

Btw. Kopete uses about 3 Mbyte of data.

`Allan
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]