[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: XML/XSD based configuration files.
From: Waldo Bastian <bastian () kde ! org>
Date: 2004-12-07 21:24:16
Message-ID: 200412072224.20364.bastian () kde ! org
[Download RAW message or body]
On Tuesday 07 December 2004 19:33, Maksim Orlovich wrote:
> > I guess it depends on your scheduler and on the amount of parsing /
> > context switch. How many config keys do you want to transfer / call?
>
> Well, the original message seems to suggest "individual keys", which IMHO
> is quite risky.
I agree.
> The (IIRC) GConf approach of pushing an entire hierarchy
> specific to the app + the globals seems reasonable.
Yes, I believe they discovered that individual keys was not good for
performance.
> A very rough indicator for this sort of thing is likely the latency of the
> konqueror-* calls that are mased by the HistoryManager --- a bit back I've
> seen that they come up as ~20ms or so per process, which is quite a lot.
> (actually, I should probably profile that again now that I understand DCOP
> better)
Would be nice to have some data indeed. Maybe we can add some test-scripts to
the dcop dir, and measure various call patterns. Would be useful later on for
comparing performance with DBUS.
> The big difficulty with a daemon-like approach, though, is deciding what
> sort of consistency guarantees it provides. If one permits the sort of
> mild races that are possible w/the current setup, it's probably not too
> hard to make it efficient. Making sure everything is in top shape, though,
> can get quite messy and expensive....
We currently provide soft guarantees by default and since KDE 3.3 we can
provide hard guarantees if the application cares enough. I think that can be
mapped relatively straight foward to a daemon approach.
Cheers,
Waldo
--
bastian@kde.org | Free Novell Linux Desktop 9 Evaluation Download
bastian@suse.com | http://www.novell.com/products/desktop/eval.html
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic