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

List:       kde-devel
Subject:    Re: KConfig again
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-05-16 10:57:15
[Download RAW message or body]

Yep, this is my general impression. Most apps read in KConfig files in their
constructors and stick the items they want into their own internal data
structures. They don't continually call readEntry(). So why cache the file in
memory if it is getting expensive to do so?

As far as writing data you are going to be hit when you sync() anyways. 

On Sat, 15 May 1999, pbrown@redhat.com wrote:
> Mosfet and I were talking, and we made the hypothesis that most apps using
> a KConfig object to a few initial readEntry()s, and then they basically
> don't touch the KConfig object again until it is time to shut down (i.e.
> destroy the object / save changes).  This means that keeping KConfig
> entries around in RAM (cached) is rather a waste.  It would seem to make
> more sense to read it dynamically off the disk when needed.
> 
> Comments?
> 
> ---
>   Preston Brown                                    Systems Engineer
>   pbrown@redhat.com                                Red Hat Software, Inc.
--
Daniel M. Duley - Unix developer & sys admin.
mosfet@kde.org
mosfet@jorsm.com

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