<quote who="Craige McWhirter">
> This explains why my GNOME managed sessions used up all my RAM ;)
>
> I switched to E, use the same GNOME apps and never use more than 32M ;)
Well, Linux doesn't *lie*, but it doesn't really make matters clear. You may
want to read the following document, which better explains how memory works
under Linux:
http://cvs.gnome.org/lxr/source/white-papers/MemoryUsage/MemoryUsage.txt
I'll give you an example from my machine. Right now. Let's look at the
panel, seeing that it gets the brunt of so much criticism. ;)
SIZE: 3372 RESIDENT: 2856 SHARE: 1956
So, whilst it maps 3372 kilobytes, only 2856 are resident in memory.
However, it happens to share 1956 kilobytes in shared libraries, which makes
sense, given the way it's built. So that leaves a whopping 900K in use...
Pretty fair game.
How about, gtop, seeing that I'm using it:
SIZE: 5452 RESIDENT: 5452 SHARE: 3920
Reality? 1532K, which seems a little excessive for a process list, but it
does do other funky stuff.
deskguide_applet:
SIZE: 220 RESIDENT: 1740 SHARE: 1312
428K doesn't seem like much, does it?
Point is, Gnome is built to work like this, much the same as KDE. So when
you hear of twits like aaronl running around talking about bloat, you know
how to do the real numbers.
- Jeff
-- [EMAIL PROTECTED] ------------------------------- http://linux.conf.au/ --
"Socks for the foot menu!" - Liam Quin (Ankh)
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
