Re: New module proposal: tracker

[Martyn Russell <martyn lanedo com>]

On 06/11/09 10:54, Alexander Larsson wrote:
> On Fri, 2009-11-06 at 10:15 +0000, Martyn Russell wrote:
> Thats cool. Although I don't think CPU load per-se is the main problem.
> CPU scheduling is pretty easy to control such that a process only runs
> when nothing else runs. The main problem is i/o costs (increased amount
> of seeks causing degradation of application i/o) and general VM
> behaviour (filling buffer caches, bumping out other apps from memory,
> etc). These things are much much harder to control and measure.

Yea, I agree. This doesn't happen that often though. We only crawl once 
on start up (which is quite cheap in my experience) and we are playing 
with the idea of only doing it initially for first time indexes. About 
this idea, the question is, how can we guarantee when the computer is 
being shutdown to not miss file updates before the next boot? There is 
also the case where we restart the monitoring daemon and we miss updates.

--
Regards,
Martyn