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

List:       kde-devel
Subject:    Re: Memory consumption in KDE 2.0
From:       Mario Weilguni <mweilguni () sime ! com>
Date:       1999-05-03 19:45:57
[Download RAW message or body]

Am Mon, 03 May 1999 schrieb Dirk A. Mueller:
>Stephan Kulow <coolo@itm.mu-luebeck.de> wrote:
>
>> the screensaver is activated by a signal. But we agree that it
>> shouldn't be in memory as long as no screensaver is active, but only a
>> very small wrapper.
>
>before adding a new wrapper, couldn't some "core" component like
>kbgndwm take over that job ?

Yes, please. Every K-Application uses ~280KB of data, so we should avoid
splitting into too much applications.

BTW, I found out that each KApplication uses 56KB of data ONLY for KCharSets.
Check this:
before new KCharSets: data=220, stk=24, exe=84, lib=5184,rss=3332 
after new KCharSets: data=276, stk=24, exe=84, lib=5184, rss=3456 

Ok, this is not much, but KDE consists of many applications, I'd say at least
10 K-Applications per session:
* kwm
* kpanel
* krootwm
* kbgndwm
* konsole * 4 (at least on my system ;-)
* kfm
* one screensaver
* maybe some tiny programs like knotes and kcontrol docked into the panel

These are 12 K-programs, consuming ~670KB of precious RAM ONLY for KCharSets.
This is TOO much. Either we use shared memory or a similar mechanism, or we try
to reduce KCharSets itself.

Mario

--
Pedaeration, n.:
	The perfect body heat achieved by having one leg under the
sheet and one hanging off the edge of the bed.
		-- Rich Hall, "Sniglets"

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