Re: [Tracker] Ready for merge

[Martyn Russell <martyn imendio com>]

Laurent Aguerreche wrote:
> Hello,
>
> Le jeudi 07 aoÃt 2008 Ã 16:38 +0100, Martyn Russell a Ãcrit :
> > Jamie,
> >
> > I think we are ready for merge if you are happy with the current state
> > of the indexer-split branch.
> >
> > If you find anything you think needs fixing before the merge. Let us know.
>
> I'm experiencing two issues with the indexer-split branch :
> - if I terminate trackerd with "kill" (to send a SIGTERM signal) sent to
> it, I see tracker-indexer still running. I can't kill tracker-indexer
> with "kill", I have to use "kill -9"

Well, the killing the daemon doesn't mean the indexer is shutdown. This
is something we have thought about but not acted on. Should the indexer
be killed when the daemon is shutdown? Perhaps Jamie has a view. I think
it probably should be. But right now it doesn't.

As for using kill -9, the indexer may not always stop immediately if it
is writing to the disk... it should stop with in a reasonable time
though. It could be worse, it could be like Evolution which continues
processing mail for 2hrs after you click the 'x' on the main window :)
Seriously though, if you see this constantly, please report a bug. It
should be totally responsive when it comes to DBus requests and shutting
down, those are priorities we have had from the onset.

> - tracker kills the performances of my hard-drive while it starts: GUIs
> of my applications get frozen!

When it starts, do you mean, when the trackerd crawls the file system or
when the indexer is indexing content?

The indexer is nice()'d at 19. We use ioprio too. We also have a
throttle in place (which I think you can configure in tracker.cfg to
mitigate speed for performance) and its default is for speed not
performance. Could you try changing that and seeing if it makes any
difference?

There might be some tweaking that is needed. I personally don't see this
issue and my machine is not state of the art. I notice it is running,
when I am playing games or really loading my system, but it is no worse
than the old tracker was AFAICR.

> Do you intend to fix these issues before the merge (notably the second
> one...)?

That totally depends on how happy Jamie is with it. The performance
issue is always going to be different from machine to machine and I feel
this is something that will be tweaked in the coming weeks. Certainly
when we start seeing Tracker on the Maemo platform and being tested
there too.

-- 
Regards,
Martyn