Re: Question on scrollkeeper-update



Ok, so if there is no Disk activity, that means everything is done in memory at that moment. So one would expect _CPU_ activity!!! This is also not the case (as i said a couple of times already). There is no IRQ being triggers, no HD activity, no CPU activity, no high memory stress, its doing _nothing_ for quite a few seconds.

(forgive my over emphesis, but we seemed to be going on loops here ;-)


Rémi Cohen-Scali wrote:

actually it does. have a look at its sources.
scrollkeeper-0.2/cl/src/install.c
Perhaps you can't see disk access is because the bigger work is done on
some dom trees. Disk access are only made when reading & writing xml
files (at start & at end ???).
To have a better understanding have a look at sources. This chunk of
code comes from Sun.

le ven 18-01-2002 à 02:28, Chris Chabot a écrit :

Yes yes, that makes perfect sence. However, i would presume that building a database would require disk, memory or CPU activity. And non of this is the case for about 20 + seconds. Its just sitting idle.

Thats the part im realy wondering about ;-)

Rémi Cohen-Scali wrote:

Build its metadata base to be able to work. It needs to update these
data because some new docs are installed

le ven 18-01-2002 à 01:45, Chris Chabot a écrit :

At the end of the gnome-core (1.5.4) compile, it runs

  scrollkeeper-update -p /var/lib/scrollkeeper

This process takes longer then it takes some packes to compile (on my compile box anyways), and seems to do no heavy disk IO (according to vmstat and 'the human ear listening to the HDs'), and CPU usage is near 0.

What is it doing, and why is it taking so long?

  -- Chris

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list



_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]