[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Startup time (RE: konqy listview configurability)
From:       Simon Hausmann <shaus () helios ! med ! Uni-Magdeburg ! DE>
Date:       2000-03-20 14:13:57
[Download RAW message or body]


I fear most time on startup is spend on resolving symbol references when
loading the shlib view components.

I think in 60% of all konqueror startup cases the user wants to see an
inode/directory resource, so what we could perhaps do is to specify
libkonqiconview, libkonqlistview, libkonqdirtree in the Makefile.am of the
konqueror binary?
(*duck* :-)

Bye,
 Simon

On Mon, 20 Mar 2000, aleXXX wrote:

> On Mon, 20 Mär 2000, David Faure wrote:
> > I wanted to add that : konqueror doesn't use kdeinit if
> > you start it manually (it's one or the other !) but it should
> > do if you use kfmclient (for instance if you click on
> > an icon on the desktop or use the icon in kicker). But this needs
> > to be checked - the code is there but I don't think I saw
> > it working finally. :)
> 
> Ahhh, that's why I didn't feel a difference ;-)
> 
> I could measure the time required by the single steps in its constructor/main
> on my K6 200, are you interested ? (AFAIK you have a quite fast machine)
> 
> > Note that using KProtocolManager::listing()
> > and reading a few values from config files (which is needed in both cases)
> > does not slow down anything at all 
> 
> "Kleinvieh macht auch Mist" in german, roughly in english "small domestic
> animals create dung too" (ouch)
> What I want to say, big apps/libs bigger on the disk and requiring more
> reallocations slowdown startup. A single addition doesn't significantly slow
> down the whole. Tons of small additions do.
> 
> 
> I think I read somewhere that
> 
> class A
> {
>    protected:
>       int i;
> }
> 
> A::A()
> :i(1234)
> {};
> 
> is slightly faster than 
> 
> A::A()
> {
>   i=1234;
> };
> 
> since the seconds extends to 
> 
> A::A()
> :i(some undefined value)
> {
>    i=1234;
> };
> 
> Of course this doesn't effect anything if you change it in one class, but there
> are probably hundreds of objects which are initialized if kde starts.
> I don't know if the compiler optimizes this or if it would help anything, but
> at least IMHO it is nicer and more C++-like code. You see explicitely which
> members are new introduced in this class.
> 
> Bye
> Alex
> -- 
> If they say it's necessary to fight in a holy war
> If they say your life is needed to protect the great ideals
> Simply say no
> Just let them feel you disagree
> 
> Die Krupps
> 

[prev in list] [next in list] [prev in thread] [next in thread]