[PATCH] bug #53345 - startkde

[Oswald Buddenhagen]

On Fri, Sep 19, 2003 at 09:01:44PM +0200, Martin Konold wrote:
> di[d] you check how startup time is affected on low end machines?
> 
i'd classify my cely @500 a low-end machine today. :)
the shell magic can be considered to come for free.
the kde-config call takes 300 ms even from warm cache, so it obviously
hurts a bit. on the bright side, this time is saved at shutdown time. :)
given that the kreadconfig takes 350 ms and starting something as
useless as ksplash ;) takes 450 ms, this might still be considered
acceptable, given that it is a useful feature to some.
oh, btw, the three lnusertemp calls take 100 ms together - why isn't
this just one call that does everything? should be trivial to make it
accept multiple arguments.

the additional xsetroot from the second patch takes some 20 ms, so this
is not worth mentioning.

anyway ... the kreadconfig/kde-config startup times are worrisome, imo.
after all, these are batch tools (well, at least kreadconfig can be
expected to be called several times in a row) - such startup times are
simply inacceptable. i'd very much vote for implementing these tools in
plain c (i.e., only one lib dependency) - it's not like _these_ tools
_need_ a translation framework or something else qt/kde is needed for
(well, one would obviously have to reimplement some kstandarddirs magic
and a make a read-only kconfig reader, but this comes close to being
trivial). it's rather a question of philosophy whether this _has_ to be
done "the kde way" or some formal cleanness can be sacrified for speed
(an order of magnitude, btw).

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.