Summary: | The GraphMaintainer hogs up CPU usage | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | S. Burmeister <sven.burmeister> |
Component: | storage | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | me, stephan.diestelhorst, trueg, woebbeking |
Priority: | VHI | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/nepomuk-core/cb0501062945872f5420aacf8f691e8ca29f39ee | Version Fixed In: | |
Sentry Crash Report: |
Description
S. Burmeister
2011-11-09 14:57:59 UTC
Same here with uptodate 4.7 branch. I also disabled the file indexing and removed nepomuk's database when it had grown to 5GB. After some time I'm again at 2GB and KMail becomes slower every day :-( Updating priority and confirming. I'll start working on the fix. Git commit cb0501062945872f5420aacf8f691e8ca29f39ee by Vishesh Handa. Committed on 15/06/2012 at 19:16. Pushed by vhanda into branch 'master'. Remove the GraphMaintainer The GraphMaintainer's job is to remove old empty graph which have somehow appeared due to buggy code. They do not really harm anyone, but this approach of removing them on startup really makes virtuoso cpu usage spike for a very long time. It would be better to have some kind of "Data Cleaning" application for Nepomuk which would migrate old data and clean up invalid data like this. M +0 -1 services/storage/CMakeLists.txt D +0 -108 services/storage/graphmaintainer.cpp D +0 -53 services/storage/graphmaintainer.h M +0 -9 services/storage/repository.cpp M +0 -3 services/storage/repository.h http://commits.kde.org/nepomuk-core/cb0501062945872f5420aacf8f691e8ca29f39ee |