Nepomuk performance

[O. Sinclair]

On 18/01/12 16:00, O. Sinclair wrote:
> On 18/01/12 15:38, Mark Greenwood wrote:
>> The reindexing old files problem still happens to me on 4.8 but I do
>> think the performance is slightly better. Still not great though. That
>> said, I have increased its allowed memory to 350MB, which is a crazy
>> amount but nothing smaller made any difference.
>>
>> Mark
>>
>> On 18 Jan 2012, at 09:43, Jörg von Frantzius wrote:
>>
>>> Hi,
>>>
>>> this isn't meant to be another bashing of Nepomuk + Strigi.
>>>
>>> I'm just wondering about its performance: right now I see a
>>> "nepomukindexer" process seemingly indexing a 1MB PDF file for
>>> minutes (where it should only be seconds). I already wondered why
>>> Nepomuk was still indexing this morning after having turned it on
>>> yesterday evening.
>>>
>>> Does anybody know what may be the reason, or what can be done about
>>> it? I already increased "Memory Usage" from 50MB RAM to 100MB in the
>>> "Desktop Search" / "Advanced Settings".
>>>
>>> Maybe there are different indexing backends to choose from, but I
>>> don't know where to configure this.
>>>
>
> interesting - I had mine at "only" 150 Mb. Put it up and am now testing
> 350 Mb to see what happens. Report will follow
>

Very interesting! After putting Memory Usage to 350 Mb suddenly 
"nepomukindexer" more or less disappeared and virtuoso-t parks at 
296-297 Mb RAM but way more healthy CPU usage. Have not seen more than 
12% and that was very shortlived, more normal 2-6 %. And indexing did 
not "freeze" on pdf files.

So suddenly usable Desktop Search but at a cost so to speak.

Sinclair