Bug 333954 - Baloo Uses Excessive Disk I/O; Problems with Torrents
Summary: Baloo Uses Excessive Disk I/O; Problems with Torrents
Status: RESOLVED DUPLICATE of bug 332317
Alias: None
Product: Baloo
Classification: Frameworks and Libraries
Component: General (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-27 11:07 UTC by boblovgren55
Modified: 2014-07-29 16:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description boblovgren55 2014-04-27 11:07:34 UTC
Baloo is not playing nice with BOINC, and it has a lot of trouble with torrents. When I have multiple torrents going, Baloo sucks 100% of 1 of 4 cores on my machine, and accesses the disk non-stop. BOINC writes to the disk very frequently, and causes Baloo to do a lot of I/O on the disk. Yesterday, baloo_file_cleaner seemed to have gotten stuck in an infinite loop, and would not stop accessing the disk. After a while I killed the process. Nepomuk never did this much disk I/O, and Baloo is so demanding on my system's resources, that I have had to exclude the BOINC directory and completely shut it off when doing torrents. Baloo doesn't need to commit so often, and I never had to exclude the BOINC or torrent directory with Nepomuk because Nepomuk never was demanding on my hard drive. Please make Baloo perform as Nepomuk did in terms of disk I/O. Thank you.

Reproducible: Always

Steps to Reproduce:
1. Start KDE
2. Run BOINC & Torrents
Actual Results:  
Baloo does excessive disk I/O

Expected Results:  
Baloo should perform better, and not be resource demanding. Infinite loop bug needs to be fixed.

openSUSE 13.1 x64
Comment 1 Vojtěch Zeisek 2014-04-28 18:10:50 UTC
This is more general problem. I have big disk, a lot of music, photos and also varius files from computer simulations full of matrices of numbers etc. Latest Nepomuk was dealing well with that, bud Ballo isn't. I have huge I/O, all the time I see top line of iotop like this (I was watching it for a while, it sits on the top regardles what I try to do):
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
 7740 idle vojta       0.00 B/s    0.00 B/s  0.00 % 99.99 % baloo_file_extractor 176879 176878 176876 176875 176874 176873 176872 176871 176870 176869
Comment 2 Vishesh Handa 2014-07-29 16:33:32 UTC

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