Bug 259517 - Virtuoso-t/nepomuk consume much too much CPU time in KDE 4.6
Summary: Virtuoso-t/nepomuk consume much too much CPU time in KDE 4.6
Status: RESOLVED DUPLICATE of bug 246678
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Nepomuk Feeder Agents (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
: 259617 261777 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-12-11 13:18 UTC by Ralph Moenchmeyer
Modified: 2011-03-14 19:18 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralph Moenchmeyer 2010-12-11 13:18:22 UTC
Version:           2.0.89 (using KDE 4.5.80) 
OS:                Linux

Recently I updated my Opensuse 11.3 (x86_64) system to KDE 4.6 Beta. Kmail migrated all my IMAP folders to Akonadi. All in all between 3 and 4 gigabytes of mail data in many, many folders. I can use Kmail without major problems (though I do not like the fact that all mails which are only marked for deletion on the imap server (cyrus) are now shown in their folders).  

My present problem is "virtuoso-t": 

Since the migration I see a (relatively) enormous amount of CPU consumption by the virtuoso-t process. Nepomuk is activated, strigi is not.

I had hoped that mail indexing by Nepomuk/Virtuoso would come to an end after some hours. But this is not the case. 

Instead the virtuoso-t process dominates CPU consumption since days (and weeks). By more than a factor of two with compared to the next CPU-hungry process - namely a virtual VM-ware machine which I use very intensively. 

To give you some numbers: After some hours of work: 

vmware-vmx : 48  minutes total CPU-time consumption
virtuoso-t:  105 minutes total CPU-time consumption

The virtuoso-t process as well as the nepomuk process have low priorities. Still very often virtuoso-t occupies one CPU core out of 4. 

virtuoso-t does not block or hinder my daily work - at least with my current workload proile. But still i have a very bad feeling about the CPU power nepomuk/virtuoso-t constantly consume. 

And of course the fact that nepomuk/virtuoso-t never seem to come to an end after the migration of the imap folders. 

Of course I can stop Nepomuk. But that was certainly not the intention with KDE 4.6 ?    
  


    

Reproducible: Always

Steps to Reproduce:
Just migrate large Imap folder structures to Akonadi in KDE 4.6 Beta. Start Nepomuk then and have a look at a process monitor. 

Actual Results:  
Virtuso-t is the most time consuming process of the whole system.And the CPU consumption never stops.

Expected Results:  
A very low background activity of nepomuk/virtuoso-t. Which should come to an end, when no new mails appear.
Comment 1 Christophe Marin 2010-12-13 13:40:38 UTC
*** Bug 259617 has been marked as a duplicate of this bug. ***
Comment 2 Steffen Schloenvoigt 2010-12-13 21:35:25 UTC
Same problem here.
I thought it may have something to do with nepomuk indexing emails.
Thererfore, I had a look at akonadiconsole but none of the nepomuk feeders seems to be doing work.
The EMail Feeder says "System busy, indexing suspended".

Best regards
Steffen
Comment 3 Ralph Moenchmeyer 2010-12-15 00:10:36 UTC
(In reply to comment #2)

Strange - nevertheless, Nepomuk is somehow involved. As soon as I deactivate Nepomuk via the KDE system settings (Desktop search) virtuoso-t behaves normally. However, Akonadi complains about the deactivation of Nepomuk. 

In my understanding Nepomuk uses virtuoso and its database processes as a backend for indexing.
Comment 4 m.wege 2010-12-19 14:23:53 UTC
May be this bug should be assigned to Nepomuk too?
Comment 5 Weng Xuetian 2010-12-27 07:54:34 UTC
This also happens if hundreds of new text file created or deleted.
Virtuoso 6.1.2
KDE 4.6 RC1
Comment 6 Christophe Marin 2011-01-01 11:39:02 UTC
*** Bug 261777 has been marked as a duplicate of this bug. ***
Comment 7 Giulio Guzzinati 2011-01-05 03:37:23 UTC
It seems somebody is working on this...

http://forum.kde.org/viewtopic.php?f=202&t=91679

I hope it will be fixed before the final release of kde 4.6...
Comment 8 Bernhard Rosenkraenzer 2011-01-05 10:13:51 UTC
duplicate of bug 246678?
Does killing the nepomukstorage process fix it for you as well?
Comment 9 Marc Deop 2011-01-17 20:55:44 UTC
The problem seems to kick in (on my system at least) whenever I set "mark all email as read on this folder". The virtuoso process then goes rocket high! :S

Regards
Comment 10 Marc Deop 2011-01-30 13:42:02 UTC

*** This bug has been marked as a duplicate of bug 246678 ***
Comment 11 Ralph Moenchmeyer 2011-03-14 19:18:51 UTC
Is solved with KDE 4.6.1 - at least in combination with Opensuse 11.4.