Nepomuk obscene memory/cpu usage

[eggbert]

I recently upgraded to kubuntu 12.10, so figured I'd finally leave nepomuk enabled to see if it would be useful. When I first boot up something called "nepomukservicesstub" runs for about 30 min, using ~ 20% of my cpu. It eventually consumes about 200MB of ram and then finally relinquishes the cpu usage. But it's still sitting there using a 200 MB of RAM.

So my question is - what exactly is it doing using that much ram and CPU? Is it supposed to use that much system resources?

If I disable it, this all goes away of course. I've also unchecked some large directories I have so it will not index them. Seems to make no difference.

Anyway, just wondering if that is the expected behavior. I would like to try it, but any additional benefit I might get from it would be hard to justify if it's going to be such a resource hog.

[vinnywright]

yup sounds about right ,,,,,, I usualy disable the file indexing part of it and it quiets down ,,,,, then install recoll and or use locate in the CLI ,,,,,,,recoll is nice however

VINNY

[eggbert]

Even with the file indexer disabled, it still consumes the same amount of resources. I wondered if it was borked somehow as I can't imagine anyone would want to use something like this that is going to suck up vast amounts of CPU and RAM. Huge cost for little reward.

[eggbert]

I found a partial solution for this, so I am posting it here in case it helps some one else.

The reason nepomuk thrashes your disk/cpu/ram on start up is because it has to watch *every* directory under your /home folder to keep the stupid ratings, tags, comments on your file in place in case you should move or rename it. (even with strigi disabled) So when it starts up it attaches an event listener to every single directory(!) In my case, this is probably in the 1,000's of directories. So it took a really long time and a lot of resources.

To make it stop adding a "watch" to every single directory, you can add the following lines to ~/.kde/share/config/nepomukserverrc

[Service-nepomukfilewatch]
autostart=false

And then restart.

After adding these lines, it should not thrash your system on a restart. (worked for me)

The trade-off is that if you use those stupid tags, ratings, comments on files, you will lose them if you move or rename them. Otherwise, everything else appears to work.

I found this information on the blog of a nepomuk developer.
http://www.vhanda.in/blog/2012/08/ne...without-files/