virtuoso-t and high CPU usage

[GoinEasy9]

Just in case anyone is having the same problem.  I've noticed virtuoso-t causing high CPU usage the past couple of weeks.  I noticed it again tonight and went searching.  It seems openSUSE was having similar problems with it, and they found that increasing the momory it uses helps with the problem.  It does look like it helped mine, time will tell.

System Settings --> Desktop Search --> Advanced Settings --> change 50mb to 512 mb.

Comments are welcome, in case it's not the correct solution.

Edit: Actually, it was the KDE forums, the guy who posted was using SUSE.

http://forum.kde.org/viewtopic.php?f=63&t=92886&start=15

[GoinEasy9]

Ok, my virtuoso-t and Nepomuk are going crazy because I downloaded the source code for KDE and it's indexing those files.  Increasing the memory decreased CPU usage, but, the computer is still indexing after 28 hours.  Even though we're talking about >100,000 files, you would think that it could index faster than that.  
 
I'm going to leave file indexing on to see how long it takes to finish.  It is making progress.

[dibl]

Out of curiosity I turned on the nepomuk service and it did work the CPU pretty hard for some hours.  When I saw this happening, I went in to the advanced settings and gave it 256MB of memory, and that seemed to be enough on my desktop system.

[GoinEasy9]

Hi dibl

I have it set up to 512mb, and, that did reduce the CPU usage from between 40 to 50, down to between 20 to 30, but it's taking a long time.  Then again, I did download all the source code for KDE 4.9 and 4.10, so, there are literally hundreds of thousands of files.  Heh, just checked, 225,830 files in index, and, it's still running, 55 hours now.  And, it's not stuck, you can see it running when you click on the Nepomuk icon.

Maybe this old Athlon 64 X2 is what's slowing it down.  I'm still going to let it run.  I want to see what the finished product looks like.

[dibl]

My data that are indexed are similar in number to yours -- 265+k of files in 5,400 directories.  But this is an i7-950 CPU overclocked to 4.2GHz, so it can handle a heavy load.

[GoinEasy9]

Well, it finally finished.  291,831 files in index.  So, I don't think I'll be using this machine to compile any code.  I still can't believe how long it took.  Oh, well.  Guess I'll move the files over to the FX-8150 machine.  I hope the UEFI bios has a legacy mode.

[Bequimão]

Did you test different searches? How long does it take to find a certain function call?

Bequimão

[GoinEasy9]

Hi Bequimao

I haven't tested any of the search abilities yet, actually, I don't know where to start, how to time the results etc.

I have noticed that every time I log into the machine, I'm greeted with about a minute or two of high CPU usage, again, due to virtuoso-t, but, the CPU goes down to a normal level after that.  There is something not right with this whole process.  Then again, I don't see anyone else posting problems, so it may be something in my setup.

[devil]

There will be more changes to virtuoso and nepomuk with 4.10.

read about them here: http://vhanda.in/blog/2013/01/what-new-with-nepomuk-4-10/

greetz
devil

[GoinEasy9]

Thanks for the link devil. I see that they made many improvements, but, still opted to leave source files out of the indexing.  Heh, I wonder why?

Even though they keep improving the indexing, the older processors seem to churn under the stress.  It's nice that they're giving us the option in nepomuk to enable or disable source files.

[Bequimão]

Thanks for the link devil. I see that they made many improvements, but, still opted to leave source files out of the indexing.  Heh, I wonder why?

Even though they keep improving the indexing, the older processors seem to churn under the stress.  It's nice that they're giving us the option in nepomuk to enable or disable source files.

System settings -> Desktop search -> Desktop query -> Customize index folders

I would stop indexing before any changes and restart it later.

Greetings,
Bequimão

[GoinEasy9]

Thanks Bequimao

I guess I missed looking at "Customize index folders", but, then again, I didn't know the effect all those source folders/files would have on the indexing.

So, it seems I can disable certain folders from the indexing in 4.9.5, 4.10 just disables source files as a default.  Thanks for pointing it out.

[dibl]

After I turned on nepomuk I noticed I had some decrease in free space on the root filesystem.  Today I tracked it down to this one, in my home folder:

Code Select Expand

~/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.db

Dolphin shows it at 1.2GiB.  So, that's one side-effect of the indexing.

[GoinEasy9]

My soprano-virtuoso.db is at 1.6Gb, well, we knew the index had to go somewhere.  Without the source code, on other machines, from 10 to 100 Mb.

Thanks for pointing that out dibl.