huzzah! kde 3.5.1 was released. congrats to all involved!
after a bit of hacking with tridge this evening, popping kde configs into ldb/tdb is down to comparable speeds with kconfig and even beating it by a slight margin at times if one turns off fsync and does per-file transactions. with fsync and per-file transactions (a.k.a. safe mode) it's hovering around the same speed, usually a tad slower though. this is a marked improvement over yesterday, to say the least.
tridge is looking at a few cases of inefficiency stemming from link list usage in the transaction code.
this is all on write. read is the next beast to tackle. and that requires revisiting kconfig itself quite a bit. i got an email from thomas braxton tonight who apparently has also been working on that particular area so we're going to combine efforts to bring the promise of multiple-backends for kconfig into reality.
i realized the other day that to do it Right, we'll have to provide for different backends based on resource type (which kconfig thankfully is already aware of) so that, for instance, application .desktop files always use the INI backend; we'll also have to provide a way to configure individual config prefixes, so that system configs can be rolled out over the network as single files using replication but users can continue to use INI files. i haven't really thought much about how to accomplish the latter; maybe thomas has ... or maybe i'll have to take a few extra showers in the coming days.
(i do my best thinking in the shower. warmth, water, white noise, gentle masssaging of the skin, nakedness. what could be more hospitable to deep thought?)