[Kde-pim] KDE 4.8, Virtuoso at 130% CPU for hours now - how can I help find the issue?

[Christian Mollekopf]

Indexing does take *very* long.

Here are a couple of points that still suck with current indexing:

* It's slow (sometimes seconds for a single message). This is mainly due to 
the merging logic in nepomuk I believe. I suppose there would be quite some 
room for improvement.

* If the initial indexing doesn't finish, and i.e. the computer is restarted, 
it starts all over. The indexing status should at least be tracked with 
collection granularity.

* Some messages still fail to be indexed (due to a problem in merging).

I'm aware of those problems and will try to fix them. The pim sprint will be 
one opportunity for this. So far I was busy getting it to work basically, I'm 
sorry that it still kinda sucks (It wasn't initially apparent to me how much 
it sucks).

Since the indexing can take days (depending on your mailbox), if you restart 
in between you might never get out of the initial indexing phase.

Here's what you can do:
* Index only what you need:
KMail -> Folder Properties -> Maintenance -> Disable fulltext indexing

* Wait until the initial indexing has finished:
It's done when you have the following line in:
.kde4/share/config/akonadi_nepomuk_feederrc

[InitialIndexing]
IndexCompatLevel=3

* add 

[akonadi_nepomuk_feeder]
DisableIdleDetection=true

to the same file to disable idle detection (Meaning it will constantly keep 
indexing => hog your cpu).

Once you manage to get over the initial indexing things should go quite smooth 
from there. But yes, initial indexing is still in pretty bad shape apparently.

Of course it's still not necessarily the problem for you, there is a bug where 
virtuoso simply goes crazy. But the feeder can also cause virtuoso to run at 
full speed (at least as soon as you stop moving the mouse), for a long time.

Cheers,
Christian

On Saturday 28 January 2012 12.27:30 Markus Feilner wrote:
> Am Freitag, 27. Januar 2012, 19:58:30 schrieb Georg C. F. Greve:
> > Hi all,
> > 
> > On a freshly installed Fedora FC16 with KDE 4.8 I set up my Kontact anew
> > since I figured maybe some issues were caused by migration cruft.
> > Unfortunately, that is apparently not so.
> > 
> > Virtuoso is the #1 resource hog on the machine, with 130% CPU constantly,
> > occasionally going to a whopping 160%, and has been doing this for hours
> > now, as well as over 200 MB of process memory. I've also seen MySQL go
> > nuts
> > on me before, although not right now - with an uptime of three hours,
> > mysqld has a TIME+ ranking of 1:47.47. Virtuoso has 183:41.11.
> > 
> > I followed the advice of http://userbase.kde.org/Akonadi and disabled
> > Nepomuk search as well as the Contact plugin, after which I restarted the
> > machine. The above numbers are *after* doing that.
> > 
> > Others, including Marcus Feilner, the journalist who shows up to the KDE
> > PIM meetings report the same issue, see
> > https://plus.google.com/105201437130417639658/posts/XPQ8DGy5ahR
> > 
> > So I think it's time we do something about this...
> > 
> > ...how can I help?
> > 
> > Is there anything in terms of debugging information I can provide that
> > would help you figure out the issue?
> > 
> > Best regards,
> > Georg
> 
> Thanks Georg!
> At least one of my systems has changed behaviour. On the desktop PC running
> Ubuntu 11.10, since today, no "huge" virtuoso-t" activity has shown. Is it
> possible that on a Quad-Core Phenom with 8 GByte RAM the indexing of some 6
> GByte Mailstore takes several days? I doubt that.
> 
> And if so, how long should I have my notebook (no change there, same
> behaviour as Georg reports, running Mint 12) attached to power...? :-)
> 
> I will have it run for the weekend, but I doubt that this is the problem.
_______________________________________________
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/