Bug 272125 - Virtuoso backgroud workers makes system usless
Summary: Virtuoso backgroud workers makes system usless
Status: RESOLVED DUPLICATE of bug 281653
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-01 10:16 UTC by Sergey
Modified: 2011-10-25 14:22 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey 2011-05-01 10:16:01 UTC 
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Virtuoso backgroud workers (virtuoso-t) makes system usless. It make too much of read\write operations so due to ugly OS scheduler system UI mostly hangs. It should be way to decrease I\O operations amount when user activity detected or way to set I\O limit for this case.

Reproducible: Always

Steps to Reproduce:
Just try to index some home directory with a lot of data
Comment 1 kde 2011-08-02 05:46:16 UTC 
I have a similar problem - it also uses a high amount of cpu processes.

At present, according to system monitor, it is sleeping AND using 96% cpu.

This clearly is not right.
Comment 2 Alejandro Nova 2011-08-08 07:15:42 UTC 
Please, retest with KDE 4.7.0.
Comment 3 kde 2011-08-08 19:32:37 UTC 
Mine was with 4.7.0.

At present it is running at around 60% and it says it is sleeping.
Comment 4 Alejandro Nova 2011-08-08 20:16:24 UTC 
Can you discard bug 278591 packaging issues? I reported that long ago and I got massive memory leaks with a lot of CPU usage because of packaging issues. You need raptor2 2.0.4, rasqal 0.9.26, redland 1.0.14 and soprano 2.7.0 compiled against all of the above. Also, if you can, try to install at least strigi 0.7.5; it can cut system load by half compared to strigi 0.7.2.

If you can discard packaging issues, have all those packages installed, and are still having trouble, please, let's have this bug as confirmed.
Comment 5 Sebastian Trueg 2011-10-25 14:22:00 UTC 

*** This bug has been marked as a duplicate of bug 281653 ***