Bug 293463 - Strigi/Nepomuk Uses too much cpu
Summary: Strigi/Nepomuk Uses too much cpu
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 17:28 UTC by Mebuntu
Modified: 2013-06-10 15:52 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Sysmon before (143.68 KB, image/jpeg)
2012-02-07 09:03 UTC, Mebuntu
Details
Sysmon graphs before (122.61 KB, image/jpeg)
2012-02-07 09:03 UTC, Mebuntu
Details
Sysmon after (114.95 KB, image/jpeg)
2012-02-07 09:04 UTC, Mebuntu
Details
Sysmon graphs after (143.02 KB, image/jpeg)
2012-02-07 09:05 UTC, Mebuntu
Details
Screenshot which shows process with high cpu load. (333.86 KB, image/png)
2012-02-09 17:53 UTC, Randy Andy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mebuntu 2012-02-06 17:28:12 UTC
Version:           unspecified (using KDE 4.7.4) 
OS:                Linux

This is a well known issue with Strigi/Nepomuk, which has been around for years.  CPU utilisation goes almost to 100% when indexing, causing system response problems, even on my quad-core i7 processor.

Reproducible: Always

Steps to Reproduce:
Leave system idle with Strigi/Nepomuk running.

Actual Results:  
When indexing starts, CPU goes to 100%

Expected Results:  
When indexing starts, CPU goes to 100%

If there's one thing that needs to be fixed, it's this!
Comment 1 Christoph Feck 2012-02-06 18:15:24 UTC
> CPU utilisation goes almost to 100% when indexing

Which process?
Comment 2 Mebuntu 2012-02-07 08:58:18 UTC
I took some screen dumps of Sysmon this morning after the machine had been left overnight, I don't seem to be able to post them though.  The combination of Nepomukserver, nepomukindexer, nepomukservicestub, and virtuoso-t seem to utilise almost 100% of a cpu, if that makes sense.  Virtuoso-t was using 349K of memory too.
I tried to exit Strigi but the services still didn't shut down so I had to kill them manually.  When I killed all those processes, the machine returned to normal cpu usage.
If there's a better diagnostic command to use let me know and I'll supply more info'.
Comment 3 Mebuntu 2012-02-07 09:03:09 UTC
Created attachment 68586 [details]
Sysmon before

shows processes when performance affected.
Comment 4 Mebuntu 2012-02-07 09:03:57 UTC
Created attachment 68587 [details]
Sysmon graphs before

Shows sysmon graphs before, with high cpu usage
Comment 5 Mebuntu 2012-02-07 09:04:55 UTC
Created attachment 68588 [details]
Sysmon after

Shows sysmon process back to normal after processes are killed.
Comment 6 Mebuntu 2012-02-07 09:05:43 UTC
Created attachment 68589 [details]
Sysmon graphs after

Shows sysmon graphs after processes were killed, with cpus back to normal.
Comment 7 Christoph Feck 2012-02-07 11:55:59 UTC
Thanks for the update. Assigning to nepomuk developers for inspection.
Comment 8 Randy Andy 2012-02-09 17:53:52 UTC
Created attachment 68656 [details]
Screenshot which shows process with high cpu load.
Comment 9 Randy Andy 2012-02-09 17:54:55 UTC
I have had the high cpu load in earlier kde versions, but it worked well for me at last in version 4.7.4.
Now on kde-4.8 the high cpu load comes back again and doesn't drop down ever, also if waiting til eternity. Also not if indexing has been finished or after deactivating it, nor if kmail has been stopped.

None of the hint given at the end here works for me:
http://userbase.kde.org/Akonadi
A new user profile or deleting my .kde directory works well, but after restoring my kontact/kmail/strigi settings, the high cpu load came back again.
Comment 10 Vishesh Handa 2013-06-10 13:03:48 UTC
With KDE SC 4.10, Nepomuk has been improved a lot and it now indexes consumes a lot less cpu. Additionally, with the 4.11 release there have been even more improvements. Now Nepomuk barely consumes any cpu on startup.

Though there are still some more areas which I can optimize. I'm working on it.

Marking this bug as FIXED.
Comment 11 Mebuntu 2013-06-10 15:52:52 UTC
great! thanks.