On Wed, Dec 15, 2010 at 11:37, Will Stephenson wrote:
I should clarify.. it doesn't block up my system... I can still use it while it's indexing (ie it's nothing like Beagle was)... I just get annoyed that it runs all cores at 100%, and my system fans all switch to high... the noise is really annoying. Once it stops its redundant re-indexing (something I think is incredibly dumb since it's already indexed everything I told it to index) then my system settles down and the fans all go quiet.
The 100% cpu usage is a bug in the virtuoso DB used by nepomuk for storage that we're trying to track down. It seems to be a relational query that makes virtuoso spin for a few minutes, that we will report as a bug to virtuoso or modify the query for.
If you want to help, install virtuoso-server from home:wstephenson:branches:KDE:Distro:Factory and next time it happens
* read the port in use by virtuoso by looking at the most recent config file in /tmp/virtuoso* * connect to virtuoso: isql -H localhost -P <port> -U dba -P dba * "status();" * and let me know the output
Cool, I'll give that a try later today. Just to be sure for those reading this thread and still hurting from their Beagle experience... Nepomuk does behave well (CPU and system I/O performance is not hit) once it has gotten past the initial CPU usage on start up thing. You don't notice it's there after it's done indexing - even on a low end machine (I use/test it on an EEE netbook as well). What about the vast amounts of disk space it chews up for the indexing? On my server/desktop machine, I've got it severely restricted what it can index (only a few directories with images, documents and multimedia files) and the Nepomuk index is over 1Gb, and David noted an even larger index. Is it "normal" for the index to grow this big? I've never turned on the backup/snapshot feature, so in theory, it shouldn't be multiple backup copies that it's using. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org