On Sat, 4 Feb 2006 12:56:27 +1000 David Seikel <[EMAIL PROTECTED]> wrote:
> On Sat, 4 Feb 2006 11:30:09 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Sat, 4 Feb 2006 04:16:28 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > It used to start up slowly for me to. So I whip out oprofile to > > > test, and now it starts up instantly. Did you fix this when I > > > wasn't looking? > > > > no??? -maybe reboot the machine (or flush all disk caches etc. etc.) > > and restart e to make sure nothing is loaded try? really all it does > > at startup is load some theme data (as e is doing ALL the time while > > it runs - nothing new) and it lists all files in your $PATH so it > > has a list of all executables to hunt through (as it will need this > > soon enough). the reason it loads it then is this list may change > > as u may install thing in between. i am suspectin g doing this > > listing is what';s slow - but why? how can simply LISTING the > > constents of maybe 10 directories (in your $PATH) take up 10 > > seconds? thats why i want to see the oprofile info. the other > > options are to literally go into the code for the exebuf show call > > and put printfs every 2nd line that print out a timestamp (from > > ecore_time_get()) as a delta from the previous timestampe they got > > and then see which call takes the most wall-clock time then go from > > there. > > Well, I'm updating now, so when that is finished I'll see what happens > after a reboot. Got the delay, profiled it, hope this helps.
oprofiled.log.bz2
Description: application/bzip
pgpv4gEt8nc4T.pgp
Description: PGP signature
