kdeinit optimization

[Waldo Bastian]

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

On Mon July 5 2004 17:37, Karl Vogel wrote:
> Some random thoughts...
>
>
> 1) Pre fork
>
> If I'm not mistaken, kdeinit will currently fork() and then dlopen
> the app when a user launches an app.
>
> I'm wondering if there would be any benefit in pre-forking kdeinit
> and then having it wait on a pipe to get the app name which is then
> dlopen'ed. That way the VMA/fork setup of the process is done before
> the actual startup of a process.

I don't think VMA/fork is the bottleneck, is it?

> 2) Re-exec
>
> Another thing I'm wondering about... should kdeinit have a way to
> re-exec?! Since a few systems are now using prelink, long running
> KDE apps will have their sharedlibs deleted by prelink, ie. my
> kdeinit shows:

I think that's typical for a workstation used for KDE development, but does 
that happen in other situations as well?

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)

iD8DBQFA6XmlN4pvrENfboIRAtKfAJ0ctwpaaZvZTGjMPcTpNy8hPpj5NgCfdeFD
A/oqqoFgra1jfsSWYQr63uQ=
=Ixmi
-----END PGP SIGNATURE-----