[Kde-pim] [Nepomuk] Problems with akonadi_nepomuk_feeder/virtuoso

[Andras Mantia]

Anders Lund wrote:

> On Søndag den 27. november 2011, Christian Mollekopf wrote:
>> By now I'm pretty sure that it is just the queue which is getting huge, I
>> managed to produce a queue of ~40'000 items which resulted in the feeder
>> using  600 megs of ram. As a workaround I could limit the queue to a
>> certain size, which would result in all lost items not being indexed
>> (until they are changed again).
>> A proper fix would probably involve queuing the items with id only and
>> then  fetching a batch of only 100 items or so, but I suppose I'm a bit
>> late for this (would need a bit of refactoring code wise)
>> 
>> Should I limit the queue to a certain size?
>> 
>> Any input appreciated.
> 
> Given the negative impact this isseue have on user experience, how can it
> be too late?
> 
I agree, even if this is a larger refactoring, the bug is serious, so any 
solution is welcome.
I also had to recreate the nepomuk database because the virtuoso-t process 
simply bruned the cpu without never ending.

Andras
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/