[arch-general] KDE update and baloo
After the update to 4.13 - i have baloo sucking up cpu cylces. I did go to the desktop search and add every single file system/directory to the 'dont scan' list. So there should be nothing left to scan. Didn't help - it's still running 2 hours later ... anyone know how to stop this selfish cpu hog? thanks!
On Thursday 17 April 2014 09:11:35 Genes Lists wrote:
After the update to 4.13 - i have baloo sucking up cpu cylces. I did go to the desktop search and add every single file system/directory to the 'dont scan' list. So there should be nothing left to scan.
Didn't help - it's still running 2 hours later ... anyone know how to stop this selfish cpu hog?
I disabled it by editing $HOME/.kde4/share/config/baloofilerc: [Basic Settings] Indexing-Enabled=false 1. https://mailman.archlinux.org/pipermail/arch-general/2014-March/035350.html -- С уважением, Е.Алексеев. Sincerely yours, E.Alekseev. e-mail: darkarcanis@mail.ru ICQ: 407-398-235 Jabber: arcanis@jabber.ru
On Thu, Apr 17, 2014 at 3:11 PM, Genes Lists
After the update to 4.13 - i have baloo sucking up cpu cylces. I did go to the desktop search and add every single file system/directory to the 'dont scan' list. So there should be nothing left to scan.
Didn't help - it's still running 2 hours later ... anyone know how to stop this selfish cpu hog?
thanks!
Is it with KDE PIM? I remember a discussion in the release ML that baloo was somewhat broken in PIM. I dunno if that was fixed or not.
On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote:
Is it with KDE PIM? I remember a discussion in the release ML that baloo was somewhat broken in PIM. I dunno if that was fixed or not.
No not using PIM. I killed off all the baloo processes - short term fix.There really should be an off button on this kind of thing.
On Thu, Apr 17, 2014 at 4:33 PM, Genes Lists
On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote:
Is it with KDE PIM? I remember a discussion in the release ML that baloo was somewhat broken in PIM. I dunno if that was fixed or not.
No not using PIM. I killed off all the baloo processes - short term
fix.There really should be an off button on this kind of thing.
I've a problem with baloo too, but with RAM usage. After a few minutes of KDE with baloo activated and indexing data in some partitions with a few hundred gigabytes of my data (video, music, big source trees of projects, VMs, etc), I experience a continuous growing in RAM usage, sometimes up to consuming my entire 12G RAM and starting paging to swap, driving my system almost unusable. Another times, RAM grows up to 4~5 Gb and stay there. I have no KDE PIM configured (no mail accounts, etc). Weird is that that amount of RAM isn't reported by htop/top/ps for being from any processes. The sum of all processes memory usage stay near the habitual 1-1.5G RAM. Logout and terminating all user processes doesn't free my memory too. The only way to get my memory back is restarting PC. But I'm sure the problem is with baloo or something related, since disabling it the problem goes away. Maybe something related with my btrfs root/home, although mentioned large data partitions are in ext4. I don't want to disable baloo, I liked it's speed in file indexing and searching, but it's unusable now. Anyone know if there's any way to fix it? Or, at least, track down where my memory gone? [maybe kernel memory? kernel caches? unfreed pages?]. Thanks -- /-=| Δ ŋ đ г Σ |=-\ «» ♫♫♫ http://www.google.com/profiles/andre.vmatos
On Thu, Apr 17, 2014 at 8:33 PM, Genes Lists
On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote:
Is it with KDE PIM? I remember a discussion in the release ML that baloo was somewhat broken in PIM. I dunno if that was fixed or not.
No not using PIM. I killed off all the baloo processes - short term
fix.There really should be an off button on this kind of thing.
What I found is after runing the current pacman update, then I did the following. Logout and back in to kde. Then once logged back in went to the kde system settings and into Desktop Search, and simply add the user home directory to the list not to search. Apply the changed setting, and then logout and back in (there was a slight delay to the logout process at this point due to the initial baloo processes running but I just waited out the half minute or so till it logged out). There was be a baloo file cleaner process running when I logged back in, which on my machines seemed to run for a few minutes only, and then stop. At that point if I checked the file: $ cat .kde4/share/config/baloofilerc and found that at the top that there were already the lines: [Basic Settings] Indexing-Enabled=false [General] several other lines after this..... At that point baloo quietened down and there were no further issues with baloo but I guess you need to have a little patience during the initial running of the processes mentioned above, so it is a short term issue only. I have seen a gentoo thread which suggests that allowing baloo to index email does give a very efficient search even for tens of thousands of mails, but of course the initial indexing process does take a little time and CPU cycles for several minutes depending on how many directories and files are in the mail area - but once that is complete then it is suggested that it works extremely well. -- mike c
participants (5)
-
André Vitor
-
Evgeniy Alekseev
-
Genes Lists
-
Lukas Jirkovsky
-
Mike Cloaked