[Nepomuk] Nepomuk::ResourceWatcher: Performance issues

[Peter Penz]

Hi Vishesh,

On 04/09/2012 09:54 AM, Vishesh Handa wrote:
[...]
>     - Invoking ResourceWatcher::addResource() after invoking
>     ResourceWatcher::start() has no effect. As workaround before adding
>     a resource I needed to invoke ResourceWatcher::stop(), add the
>     resource and invoke ResourceWatcher::start() again. The problem with
>     this workaround is the performance: Calling stop() clears e.g. 15000
>     items and calling start() after adding one resource adds 15001 items
>     again. In the case of the directory with 20000 this might take up a
>     few seconds for each (!) of the items in the upper-range.
>
>
> I see.
>
> Btw, from a performance perspective, it would be better if you only
> monitored the resources and properties you're interested in. In your
> case that would be nao:numericRating and nao:hasTag.

Ok, I'll try to improve this.

[...]
>     It would be great if this could be fixed by the Nepomuk-team but I'm
>     aware that your time is limited. So my question: Should I submit a
>     bug-report and is it realistic that you can fix this before 4.9.0?
>     Or should I try provide a patch?  My time is also limited and I'd
>     prefer the "Nepomuk-team-fixes-it"-__option, but without a fix this
>     would be a kind of showstopper from a Dolphin perspective and... -
>     well, I'd provide a patch if you cannot work on this ;-)
>
>     Still crossing my fingers that you say "no big deal, easy fixable"...
>
>
> I'll try it out and look at it.
>
> I'm a little busy till Friday, so I'll probably look at it over the weekend.

That would be really great, thanks! If it makes it easier for you, 
please feel free to send me early versions of your patch and I'll check 
whether it works with the Dolphin-usecase.

Cheers,
Peter