Dynamic symbol table

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 16 July 2004 00:23, Frans Englich wrote:
> Optimizing KDE startup has been pondered many times before -- check the
> archive, it got much to tell.
>
> (Disclaimer: I have no idea what I'm talking about)
>
> Regarding modules, one way I thought of startup optimization was to make
> kcminit threaded in order to keep IO busy and do useful stuff while
> syscalls sleeps. Many of these init kcms deals with hardware and they may
> sleep for long times in their sycalls. For example, I once measured how
> long the kmix kcm took to initialize on my (broken) setup: 5 seconds(hot
> cache). Anyway, threading could be an idea. To avoid IO trashing the code
> could sleep small amounts of time between the spawning of threads(an
> average determined by testing different setups, or calculated in some
> intelligent way).
> Could anyone who actually knows about this stuff deny/"write a
> patch"/elaborate? :)

KDE in general and by extension kcminit modules in general are not thread safe 
so that's a bit of problem, we can't just put them all in threads... what we 
might be able to do is:
1) dlopen the modules in different threads
2) allow the init modules to start worker threads that run while kcminit runs 
the next init module.

But I guess we need to start with making some visualization tool to understand 
the scope of kcminit in the problem and to measure the improvement once we 
have developed such a scheme.

Cheers,
Waldo
- -- 
bastian at kde.org  |   KDE Community World Summit 2004  |  bastian at suse.com
bastian at kde.org  | 21-29 August, Ludwigsburg, Germany |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFA97I6N4pvrENfboIRApLPAJwNmNrFedc2NYwuEuz+1qnu51v38QCfe8QO
FHz8VH8d6GfbwIhgqXBybNw=
=Z+Un
-----END PGP SIGNATURE-----