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

List:       kde-core-devel
Subject:    Re: kconfigbackend::parseconfigfiles()
From:       Waldo Bastian <bastian () suse ! de>
Date:       1999-12-10 9:09:35
[Download RAW message or body]

On Fri, 10 Dec 1999, Mario Weilguni wrote:
> I found a really strange behaviour in KConfigBackend. I noticed that it called 
> a function findAllResources(), which simply walked over ALL config files in
> ~/.kde/share/config/ only to find one file which name is exactly known
> "kdeglobals", and a second call with "system.kdeglobals". 
> 
> This is really bad, and results in ~220 stat() calls on startup of every, no
> matter how simply KDE program. Has anybody a clue why it works this way?

This was the easiest way to implement the general case.

> If this is needed by design - then we should really consider changing the
> design. Suppose a NFS mounted home directory, it will be slow as hell. And even
> on local harddisks, it will produce a lot of noise on low mem machines.

It is easy to optimize findAllResources() for the case where only a
single file needs to be found. I will do it.

Cheers,
Waldo

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