Page 1 of 3 123 LastLast
Results 1 to 10 of 29

Thread: Baloo Using Excessive Disk I/O

  1. #1
    Join Date
    Jan 2014
    Location
    United States
    Posts
    150

    Default Baloo Using Excessive Disk I/O

    After upgrading to KDE 4.13 through the Factory repo, I had issues with Baloo going crazy when BOINC was running, as BOINC writes to the disk constantly and Baloo went completely nuts trying to index everything in that folder. I excluded the BOINC directory in the Desktop Search GUI and the problem went away, and disk I/O returned to normal.

    After removing the KDE factory repos and adding the KDE current ones, there were some more updates for KDE, xorg, etc. I'm assuming there were some more changes between the time the packages moved from one repo to another. Running iotop shows that baloo_file_cleaner is taking around 50% IO when absolutely nothing is running on the computer besides Linux kernel modules, KDE desktop, etc, and this has been going on for hours. I figured it may be indexing my files, but I don't get why it would be re-indexing everything when Baloo had already indexed stuff after applying the first KDE 4.13 update. The Desktop Search GUI should offer a way for a user to disable the program, and I'm not the only one having this issue. My presumption is that Baloo is indexing nothing, and is stuck in some kind of endless loop. Just when Nepomuk was working good, they had to change it and release this complete garbage. Not only is Baloo broken, but they didn't offer novice users a simple way to shut it off. Real smart thinking KDE devs.

    http://ubuntuforums.org/showthread.php?t=2217434

  2. #2
    Join Date
    Jan 2014
    Location
    United States
    Posts
    150

    Default Re: Baloo Using Excessive Disk I/O

    More comments from frustrated users:

    http://vhanda.in/blog/2014/04/deskto...configuration/

    Here's a tip for everyone: Don't upgrade to KDE 4.13 like I did.

  3. #3
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Baloo Using Excessive Disk I/O

    On 04/26/2014 12:06 AM, pirithous wrote:
    >
    > More comments from frustrated users:
    >
    > http://vhanda.in/blog/2014/04/deskto...configuration/
    >
    > Here's a tip for everyone: Don't upgrade to KDE 4.13 like I did.
    >
    >


    1. Nepomuk was *not* just working (at least on my system), it used quite
    a bit of memory, especially if you tried to use it to do heavy indexing.

    2. I am using 4.13 and its working like a charm on my system. Baloo and
    Milou are really impressing me with their low memory usage and useful
    indexing.

    With that said, you can check what Baloo is doing with this command
    Code:
    qdbus org.kde.baloo.file /indexer org.kde.baloo.file.statusMessage
    Also check in ~/.local/share/baloo to see if it is writing to the
    location because that is where it keeps its database.
    --
    Bring the Penguins Back! https://features.opensuse.org/316767
    openSUSE 13.1
    KDE 4.11.4

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,396
    Blog Entries
    1

    Default Re: Baloo Using Excessive Disk I/O

    2. I am using 4.13 and its working like a charm on my system. Baloo and
    Milou are really impressing me with their low memory usage and useful
    indexing.
    I can only report the same

  5. #5
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    970

    Default Re: Baloo Using Excessive Disk I/O

    On this thread https://forums.opensuse.org/showthre...om-KDE_Current some additional information and observations.

    On my desktop 13.1/KDE 4.12.4-->4.13.0, it took baloo_file_extractor almost 7 hours to do it's first thing after upgrade, now all is quiet with baloo running.
    Desk: i7-4790K Leap 15.1(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0
    Lap: HPDV7T i7 Leap 15.0(x86_64)4.12.14-lp151.28.7-default KF5 59.0 Plasma 5.14.4 Qt 5.13.0

  6. #6
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Baloo Using Excessive Disk I/O

    Quote Originally Posted by cmcgrath5035 View Post
    On this thread https://forums.opensuse.org/showthre...om-KDE_Current some additional information and observations.

    On my desktop 13.1/KDE 4.12.4-->4.13.0, it took baloo_file_extractor almost 7 hours to do it's first thing after upgrade, now all is quiet with baloo running.

    Yep same here, the initial indexing took a really long time but now its not doing it anymore. But even when it was indexing stuff, I only saw it use up one core on the CPU while the RAM usage stayed pretty stable at 1.6GB. The only time I saw RAM go crazy is when you tell it to blacklist a folder it has already indexed, then the RAM usage goes from 1.6GB to 3.6GB
    openSUSE Leap (42.1) 64 bit
    Plasma 5.4

  7. #7
    Join Date
    Jan 2014
    Location
    United States
    Posts
    150

    Default Re: Baloo Using Excessive Disk I/O

    When downloading files such as a torrent, Baloo causes non-stop accessing of the disk, and sucks 25% of one core as long as the download is going. Nepomuk never used to do that, and whoever was praising Baloo for its great performance obviously doesn't download things such as torrents.

  8. #8
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Baloo Using Excessive Disk I/O

    Quote Originally Posted by pirithous View Post
    When downloading files such as a torrent, Baloo causes non-stop accessing of the disk, and sucks 25% of one core as long as the download is going. Nepomuk never used to do that, and whoever was praising Baloo for its great performance obviously doesn't download things such as torrents and is just saying how great it is.
    I have a 955BE as a CPU and just today I created ~50GB of files for a backup and didnt notice anything change. How is your system setup and what are your specs?

    Also i do agree that it is strange you cannot disable Baloo.
    openSUSE Leap (42.1) 64 bit
    Plasma 5.4

  9. #9
    Join Date
    Jan 2014
    Location
    United States
    Posts
    150

    Default Re: Baloo Using Excessive Disk I/O

    Core i5 2500k, 8 GB memory, 1 TB hard drive. Not only did baloo_file_cleaner get stuck in an infinite loop yesterday and I had to kill the process, but as I wrote, Baloo doesn't play nice with torrents, BOINC, or anything that is writing to the disk a lot. It tries to index immediately, and sucks CPU resources. Look around the internet...i'm not the only one experiencing issues.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,396
    Blog Entries
    1

    Default Re: Baloo Using Excessive Disk I/O

    Quote Originally Posted by alanbortu View Post
    I have a 955BE as a CPU and just today I created ~50GB of files for a backup and didnt notice anything change. How is your system setup and what are your specs?

    Also i do agree that it is strange you cannot disable Baloo.
    Actually, baloo can be disabled, but not by a simple disable button. Instead, just exclude the users $HOME directory in System Settings > Desktop Search, then you'll find there is nothing left to index, and baloo will switch off

    Before excluding
    Code:
    ps -A|grep baloo
     1238 ?        00:00:01 baloo_file
    After, it will be gone.

    Simple.

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •